activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Davies <>
Subject Re: Lost Messages and Embedded Broker
Date Fri, 28 Sep 2007 15:28:17 GMT

do you have a test case for this? This sounds like a bug



On Sep 28, 2007, at 3:34 PM, ttmdev wrote:

> If your client is starting an embedded broker via the vm or peer  
> connectors
> and sends a message immediately after invoking connection.start(),  
> that
> message will most likely fall into a black hole and your client is  
> never
> notified of this. This is because the embedded broker has not been  
> fully
> activated by the time you send the message. There is a warning on  
> the web
> site re this with an accompanying Spring-dependent work-around.  
> However, I
> would prefer not to rely on Spring. The connection.isStarted()  
> method does
> not help and neither does a transportListener. Other than forcing a  
> delay
> after connection.start(), does anyone else know of a more elegant  
> way to be
> notified that the embedded broker is ready to rock-n-roll and thus  
> safe to
> start sending messages?
> Joe
> -- 
> View this message in context: 
> and-Embedded-Broker-tf4534900s2354.html#a12941763
> Sent from the ActiveMQ - User mailing list archive at

View raw message