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 MQ Enterprise : 7.0.1 (Fix For Version)

Release Date: 04/Sep/12
Description: 7.0.1 release
7.0.1 7.0.1 release 2012-09-04T00-00

Select:

Summary

Popular Issues

ENTMQ-24	FIXED	Should karaf.name be "FuseMQ" instead of "root"?
ENTMQ-70	FIXED	How can more than two broker networks be configured
ENTMQ-64	FIXED	Allow registration in fabric discovery (zk) from standalone mode
ENTMQ-37	FIXED	Client says Apache Karaf Client in the help screen
ENTMQ-62	FIXED	Creating master-slave fails occasionally
ENTMQ-72	FIXED	Executing mq-client jar fails with NoClassDefFoundError on org.apache.commons.LogFactory
ENTMQ-59	FIXED	Increase the producer flow control mem limit and remove vmcursor in the default activemq.xml
ENTMQ-61	FIXED	Recoverable exception when starting cluster example
ENTMQ-52	FIXED	Standalone broker is still started even when the FuseMQ instance joins a fabric cluster and becomes a managed node.
ENTMQ-46	FIXED	Web console not formatted properly on first access
ENTMQ-65	FIXED	cluster-list shows brokers as master/slave when brokers are not master/slave.
ENTMQ-77	FIXED	mq-web-console feature's bundles are not distributed in system repo
ENTMQ-76	FIXED	All commands in the bin directory get "[: 27: client: unexpected operator" warning on Ubuntu
ENTMQ-57	FIXED	Log file is named karaf.log instead of fusemq.log