-
1. Re: A question about setting SuckerPassword
kmaslowski Mar 17, 2010 3:49 PM (in response to thomas2008ch)You should set unique password for all instances. To do that set it like this:
<attribute name="SuckerPassword">INSTANCE_PASSWORD</attribute>
Regards
-
2. Re: A question about setting SuckerPassword
thomas2008ch Mar 18, 2010 5:20 AM (in response to kmaslowski)I check the configuration of our all Jboss server instances and find there is only "<attribute name="SuckerPassword"></attribute>" there. What does this mean? No password or default password?
If I set the SuckerPassword as you wrotem, for exampel:
<attribute name="SuckerPassword">HelloWorld</attribute>
Should I restart the JBoss instance and what an influce will happend to the applications which deployted on it? I hope there should be no any influence.
-
3. Re: A question about setting SuckerPassword
thomas2008ch Mar 18, 2010 8:35 AM (in response to thomas2008ch)Besdies, I read fomr the document from RedHat that
"JBoss Messaging internally makes connections between nodes in order to redistribute messages between clustered destinations. These connections are made with the user name of a special reserved user. On this parameter you define the password used as these connections are made. After JBossMessaging 1.4.1.GA you will need to define the Sucker Password on the ServerPeer and on the SecurityMetadataStore."
I wonder what is this special reserved user?