Just to add to my previous post. I waited 5 minutes while the app was hanging. I fired up the local active mq broker and within a few seconds the app stopped hanging and continued on. I can't tell if the ConnectionFactoryProperties setting is being ignored but it seems telling to me that once the local active mq broker is running that it continues. Since I have no failover configured why would it use the local amq broker?
Looking at the source (and with some guesswork) I assume the ActiveMQXAConnectionFactory in instantiated using the default constructor, thereby setting brokerURL to the value of DEFAULT_BROKER_URL. It appears that when the first message is put onto the queue that the connection is established. I further assumed that setProperties(Properties props) (from JNDIBaseSortable which ActiveMQXAConnectionFactory extends) is called, which in turn calls buildFromProperties(props) which should then set the brokerURL to my setting. It's my belief that setProperties(Properties props) is not being called. -- View this message in context: http://activemq.2283324.n4.nabble.com/Connection-to-a-remote-active-mq-broker-tp4042508p4073152.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
