[jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1713) ClusterPullConnectionFactory depends on ClusteredConnectionFactory to ensure correct message sucker creation

ClusterPullConnectionFactory depends on ClusteredConnectionFactory to ensure correct message sucker creation ------------------------------------------------------------------------------------------------------------ Key: JBMESSAGING-1713 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1713 Project: JBoss Messaging Issue Type: Bug Components: Configuration and Management Affects Versions: 1.4.4.GA, 1.4.3.GA, 1.4.0.SP3.CP08 Reporter: Howard Gao Assignee: Howard Gao Fix For: 1.4.0.SP3.CP09, 1.4.5.GA ClusterPullConnectionFactory need replicator (messaging office) to broadcast its creation after it has been started and registered with the ConnectionFactoryJNDIMapper. But the ClusterPullConnectionFactory doesn't retrieve the replicator in its startup process. It replies on the ClusteredConnectionFactory to do the job. See ConnectionFactoryJNDIMapper.registerConnectionFactory(..): if (supportsFailover || supportsLoadBalancing) { setupReplicator(); } That means if the ClusterPullConnectionFactory is started before the ClusteredConnectionFactory, the replicator will not be available and its creation can not be broadcasted to other nodes, therefore the message sucker will not be created. We need to put a dependency to the ClusterPullConnectoinFactory's mbean configuration in connection-factories-service.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira