Ok, thanks for the information regarding failover. I'll be definitely looking forward to Release 3.0.
Now to the second part of my question: What is the recommended way to deal with multiple threads? Should I use the SessionPool? Or should I share one session and protect it? Any hints how to best deal with recreating the resources? Thanks and Regards, Patrick Timothy Bish wrote: > > Currently the only way to detect and recover from a broker disconnect is > to set an Exception Listener on the Connection and when it fires you > should recreate the resources you were using. > > We are currently working on V3.0 of ActiveMQ-CPP which will include > failover support but until then the recovery process is a manual one > that the user must implement. > > Regards > Tim. > > On Sun, 2009-01-18 at 22:42 -0800, Patrick Ruckstuhl wrote: >> Hi, >> >> does someone have a real world example for using CMS? >> >> My situation is the following. >> >> I have an application that has multiple threads and sends and receives >> messages. ActiveMQ itself is running on a different host so it is >> possible >> (and happens form time to time) that the network connection is lost and >> therefore we need to handle this situation. >> >> I found a SessionPool in the cmsutil package, is this the recommended way >> to >> deal with it (have a SessionPool and each threads gets a session from >> there). What's needed to set it up? Does it deal with lost connections or >> if >> not how else can I deal with it? >> >> Thanks and Regards, >> Patrick > -- > Tim Bish > http://fusesource.com > http://timbish.blogspot.com/ > > > > > -- View this message in context: http://www.nabble.com/Real-world-example-for-CMS--tp21537664p21546359.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
