Re: deadlock on com.swiftmq.tools.concurrent.Semaphore?

FYI: the behaviour I described gone away when the application has been rewritten to use only one connection, with multiple sessions. Before it used a new connection for each session, which apparently does not work well with the JMS implementation by SwiftMQ.