oh...I forgot to mention that I use 4.1.2 instead of 5 service.waitUntilStopped(); This function seems not apply for 4.1.2....
Jean rajdavies wrote: > > > On 18 May 2009, at 09:32, JS75 wrote: > >> >> Dear Sir: >> Here is my scenario - multi-producers and multi-consumers in the same >> application. >> I am sure all consumers and producers are closed before I close the >> application. >> And please note that I close the application by terminate JVM. (so I >> may not >> close broker properly?) >> So sometimes I found some messages lost and I am sure my producer >> has sent >> to queue. (use asyn send) >> I try to make thread sleep for 5 minutes and it reduces happening. >> But I need to know the correct solution of how to close embedded MQ >> properly >> (after its internal work). >> >> pleasure for your reply :-) >> >> -- >> View this message in context: >> http://www.nabble.com/How-to-know-whether-embedded-broker-is-stoped--tp23593255p23593255.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > > this FAQ entry will point you in the right direction - > http://activemq.apache.org/how-do-i-restart-embedded-broker.html > basically call waitUntilStopped() after calling stop() on the broker > > > > cheers, > > Rob > > Rob Davies > http://fusesource.com > http://rajdavies.blogspot.com/ > > > > > > > > > > -- View this message in context: http://www.nabble.com/How-to-know-whether-embedded-broker-is-stoped--tp23593255p23610960.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
