Hello All,
I've successfully written a .NET Compact Framework client that can send and
receive messages using the new NMS Stomp packages (Excellent work!)

I'm now trying to cater for dropped connections. The application will have
to receive messages, even if it has to recover from communication failures
(3G/GPRS connection interruptions). Therefore I've used two methods

ConnectionInterruptedListener
ConnectionResumedListener

The ConnectionInterruptedListener should pick up a lost connection where I
gracefully tidy up a couple of things. Then I use ConnectionResumedListener
to re-establish a connection with activemq.

The strange thing is that none of these listeners are working when I cut the
connection. Currently I'm doing this in the Pocket PC WM5.0 emulator by
switching off the network connectivity from the emulator (not gracefully).
When I restart the connection the appropriate listener does not fire, and of
course I've lost connection to activemq, but neither the server or the
consumer is aware of this.

Any ideas?
-- 
View this message in context: 
http://old.nabble.com/NMS-not-listening-properly-to-Connection-Interrupted-and-Connection-tp27324812p27324812.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to