Hi, I am having some problems setting-up an embedded broker to work correctly with a standalone broker via a static bridge - messages are getting lost. I am new to activeMQ so this is probably either a misunderstanding on my part or configuration problem.
I have a standalone activeMQ instance which routes messages on a topic to various client-specific queues. To enable the webapp to work when this standalone instance is down, I have also set-up an embedded broker in the webapp. The idea here is to allow the app to generate and send events to the local broker (using vm transport) and to have these picked-up and routed via the standalone broker, when it is active. Everything seems to work ok, but messages sent to the local broker when the standalone is down are not forwarded to the standalone broker when it is started. Is this the expected behaviour? How can I set things up so that I do not loose these messages/events when the standalone is down? Config of standalone broker (currently using kahaDB for persistence): Config of embedded broker (currently using JDBC with postgres for persistence): -- View this message in context: http://activemq.2283324.n4.nabble.com/How-to-use-embedded-and-standalone-broker-bridged-together-tp4676540.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
