sbs1982 wrote:
>
> is there some know issue of close method of consumers locking?
>
We have experienced this too, although I have not yet determined if the
problem is in Spring.NET or NMS. I'm having an impossible time tracking it
down because if I put the debugger on it the behavior changes. Even with
full logging on all components, there is not enough detail to indicate what
the root cause is.
I've been meaning to whip up a pure NMS version of a sample app that mirrors
our code (to eliminate Spring.NET as the problem) but haven't gotten that
far yet.
I did manage to capture a few details in
http://www.nabble.com/thread-deadlock-issue-in-NMS-to20180687.html#a20180687
this thread but until I can put together a test case I don't think the NMS
team has enough to work with.
--
View this message in context:
http://www.nabble.com/is-ISession-thread-safe--tp21589189p21811468.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
