[
https://jira.jboss.org/browse/JBMESSAGING-1815?page=com.atlassian.jira.pl...
]
Howard Gao resolved JBMESSAGING-1815.
-------------------------------------
Resolution: Rejected
On second thought I don't think it should be 'fixed' in the branch. It would
be better not to remove this line from the branch. Reason:
It will make the user set up cluster easier. To setup a non-clustered node the user can
manually remove this line. Even the user doesn't remove , it won't affect the
functionality.
But if the user forgets to 'add' this line when setting up the cluster, the
message sucker won't work and that may cause the user some time to figure that out.
So I reject it.
Non-clustered ServerPeer configuration doesn't need
ClusterConnectionManager to be started
------------------------------------------------------------------------------------------
Key: JBMESSAGING-1815
URL:
https://jira.jboss.org/browse/JBMESSAGING-1815
Project: JBoss Messaging
Issue Type: Bug
Components: Configuration and Management
Affects Versions: 1.4.0.SP3.CP10, 1.4.7.GA
Reporter: Howard Gao
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP11, 1.4.8.GA
In a non-clustered node, the server peer doesn't need clusterconnectionmanager to be
started which consumes startup time and resources. Simply remove this line
<attribute
name="ClusterPullConnectionFactoryName">jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory</attribute>
from messaging-service.xml will solve this problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira