Hello, I got a little further in finding some indication what's happening. My best guess is that there are race conditions...
The problem I have is when I first create and initialize the broker ... some time passes, and then I start the broker. IF I immediately start the broker after creating and configuring it, it does not block ! But nicely tells me that it cannot reach the remote broker (loops in timeout messages). When I do start the remote broker, it connects to it. BUT, now a NEW problem arises. When a JMS client ( message consumer) connects too soon to the broker address ( < 2 sec after starting at my machine), it does not have any connection errors, but it never receives any messages that are posted ! Situation: SENDER 1 ---> JMS A <- topic_x -> JMS B <--- RECEIVER 2 / receiver 3 flow: - JMS A has a NetworkConnector to JMS B - forwards topic_x to B - JMS A starts prior to JMS B - sender 1 starts posting messages on topic_x - JMS B starts - immediately connect receiver 2 to B, and listen on topic_x => no messages ! - when, after a couple of seconds, receiver 3 connects on same topic_x, it DOES see the incoming messages, receiver 2 is still silent !!! I have found no way to check if 2 can receive any messages (shows no errors, acts as normal, etc...) Is this a possible bug ? I have tried to run an example of their test (as posted in the reply). It gives the exact same behaviour : the receiver 2 does not hear any messages when it is started too soon after JMS B starts. Does anyone has the same problems ? -- View this message in context: http://activemq.2283324.n4.nabble.com/JMS-Bridge-with-static-URL-blocks-at-startup-tp3054999p3056959.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
