Browse Version - FuseSource Issue Management

Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .

All Projects : FUSE Message Broker : 5.4.2-fuse-02-00 (Fix For Version)

Release Date: 11/Mar/11
Description: Scheduled maintenance release
5.4.2-fuse-02-00 Scheduled maintenance release 2011-03-11T00-00

Select:

Summary

Popular Issues

MB-755	FIXED	Missing messages in durable subscription with selector and KahaDB
MB-829	FIXED	Consumers won't get msgs after JMX operation removeMatchingMessages() was called on a queue.
MB-818	FIXED	5.4 broker always sends out peer URIs which 5.3 clients always add to failover list
MB-831	FIXED	> Wildcard does not seem to match for all trailing elements
MB-752	FIXED	Add setTrustStore() and setKeyStore() methods to ActiveMQSslConnectionFactory class
MB-833	FIXED	Allow JAAS GuestLoginModule to fail if users specify a password
MB-812	FIXED	Can only have one duplex networkConnection per transportConnection
MB-722	FIXED	Cannot browse queues with bytes messages via JMX
MB-757	FIXED	KahaDB doesn't clean up old log files
MB-804	FIXED	NetworkConnection initialization should be backed by an executor
MB-740	FIXED	Provide a tuning guide and best practices for ActiveMQ
MB-797	FIXED	Recovering durable subs with priority and JDBC store - total message table scan is too slow
MB-819	FIXED	Virtual destinations and wildcards
MB-824	FIXED	When two loging modules configured, one succeeds, one fails but both are adding their principals
MB-834	FIXED	using durable subs messages stay in KahaDB indefinitely if broker is restarted
MB-822	FIXED	Please clean up log messages when connecting to the broker using STOMP client with a wrong name/password pair.