[jboss-user] [JBoss Messaging] - Clustered server preference

JBoss AS 4.2.2.ga, JBM1.4.0.SP1. I several clients that connect to a 2 machine cluster (devapp1 and devapp2). Below is the JMSProvider I use. On one machine I have the naming provider with devapp1 first in the list. On the second I have devapp2, as shown here. The second machine always connects to devapp1 unless I completely remove the reference to devapp1 from the list. Then it it will connect to devapp2. I thought it was supposed to try to connect in the order that they are listed in java.naming.provider.url. Is this an incorrect assumption? I am able to determine which machine it has connection by looking at the number of consumers the app servers have connected to them. <mbean code="org.jboss.jms.jndi.JMSProviderLoader" | name="jboss.messaging:service=JMSProviderLoader,name=ConversionJMSProvider"> | <attribute name="ProviderName">ConversionJMSProvider</attribute> | <attribute name="ProviderAdapterClass"> | org.jboss.jms.jndi.JNDIProviderAdapter | </attribute> | | <attribute name="FactoryRef">ClusteredXAConnectionFactory</attribute> | <attribute name="QueueFactoryRef">ClusteredXAConnectionFactory</attribute> | <attribute name="TopicFactoryRef">ClusteredXAConnectionFactory</attribute> | | <attribute name="Properties"> | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces | java.naming.provider.url=jnp://devapp2.qa.cin.int:1100,jnp://devapp1.qa.cin.int:1100 | jnp.disableDiscovery=true | jnp.partitionName=dev.application | jnp.discoveryGroup=228.1.2.4 | jnp.discoveryPort=1102 | jnp.discoveryTTL=16 | jnp.discoveryTimeout=5000 | jnp.maxRetries=1 | </attribute> | </mbean> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144247#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...