For the most part, once a cluster has been set up using the JmsFlow, everything is now flowing between components in the cluster as expected.
But...there's always a but, especially on Friday...the trick now seems to be getting the cluster up in the first place. In this scenario I have three nodes, on the same host. Each node fires up its own ActiveMQ instance, and connects to it via the following mechanism: flowName="jms?jmsURL=reliable:(tcp://<activeMqInstance1>,tcp://<activeMqInst ance2>,tcp://<activeMqInstance3>), where activeMqInstance 2 and 3 are the ports for the other nodes in the cluster. So I startup node1, and wait for it to come up cleanly. Then I start node2, and wait for it to startup, and then exchange information with node1 via ActiveMq. And I wait...and wait some more, and it never connects. Or, it connects right away. If it doesn't connect I have to bounce one or both of the nodes. Adding the third node further complicates the procedure - but ultimately I have to bounce each node before they are all fully crossed referenced. I assume that this should not be the case? This is using 2.1, version 992. regards, /jonathan
