I am currently taking a look at this. Part of the solution is to set a timeout for your transport using a URI parameter like so:
activemq:tcp://amqsrv:61616?transport.requesttimeout=10000 Where requesttimeout is in milliseconds. However, there is a bug with the timeout, because it will continuously retry after the timeout expires. I hope to have a fix for this soon. On 4/2/08, jeetukiran <[EMAIL PROTECTED]> wrote: > > The NMS API calls to send and receive messages synchronously hang when the > connection to ActiveMQ gets broken, the expections are not relayed back to > the caller. > -- > View this message in context: > http://www.nabble.com/NMS-library-hangs-when-connection-to-ActiveMQ-is-broken-tp16452218s2354p16452218.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
