On Mar 7, 2010, at 1:00 PM, Bruce Snyder wrote: > Yes, this is Rob's recommendation. Below is a depiction of how it should work: > > brokerA-old --(network connection)--> brokerB-new > > * brokerA-old is configured to use the AMQ store > * brokerB-new is configured to use the KahaDB store > > Message consumers connect to brokerB-new to consume messages from a > destination that already exists on brokerA-old. When messages are > forwarded from brokerA-old to brokerB-new, they are extracted from > brokerA-old's AMQ store and inserted into brokerB-new's KahaDB store.
Won't the messages stay on BrokerA until a consumer on BrokerB asks for them? Then wouldn't it be pretty transient. The message would be removed as it was consumed right? Could BrokerB could be setup to consume the messages and store them local using <jmsTopicConnector> or <jmsQueueConnector>? That would pull them local to BrokerB and stored in KahaDB. Can the same thing be achieved with a network connection?
