Hi Dan. I've experienced similar problem, though I use SSLServlet transport for JBM. I've described my issue in the post:
Initially I had blocking problem but after I overcome it, it appears non-reliable client-side MessageListener. I'll track this topic for possible hints and ideas. Thanks.
Thanks for replying. Having looked at the details of your issue it doesn't really seem to apply to us as we aren't using MDBs or 'chaining' destinations, and there wasn't anything in the client stack trace. We didn't really look at a stack trace of the broker. However it should be noted that when we disconnect the consumer and reconnect much later on (at least 10 minutes, so unlikely to be a timeout), the messages do get delivered to the new consumer. We're only using JMS in a very simple way for testing purposes at the moment. Unfortunately it still seems to be failing in a pretty worrying manner! Thanks, and any thoughts anyone else has on how to further diagnose this issue would be much appreciated.