I have finally resolved several issues and am now seeing some messages sent
to and processed on the remote server! As your said, a big problem ended up
being the different point releases of the JVM (1.5.0_06 vs. 1.5.0_10).
Another problem seemed to be that I had multiple transport connectors
specified for the broker and was not consistently using the same one for
everything (e.g., using "peer://localBroker-${HOSTNAME}" for the connection
factory.) This seemed to cause more than one ActiveMQ instance to be
started up in the same JVM. After I specified the JMS URL & broker URI
consistently as tcp://localhost:61616 and only saw one ActiveMQ being
started, I was then seeing the same message being processed on both servers,
but this problem vanished after I removed all transport connectors from my
broker except the one I was using with tcp (above.)
Thank you so much for your help,
Ellen
--
View this message in context:
http://www.nabble.com/Endpoint-Determination-Made-By-Flow-in-a-Clustered-Environment--tf2868246s12049.html#a8170506
Sent from the ServiceMix - User mailing list archive at Nabble.com.
