Leos Bitto wrote:
... which apparently does not work well with the JMS implementation by SwiftMQ.
We have no open issues here and if there would be issues, this would be fixed ASAP.
First, there were no deadlock so the title of your post is misleading. Next, a request timeout can happen under some circumstances (n/w buffer extension, OOM). Since you didn't answer my questions above, I assume you are not willing or able to go further into this issue. On the other hand, if it works with a single connection, you save n/w buffer space (avoid OOM) and save CPU time because there is only a single connection where the n/w buffers need to be extended. So you don't see this behavior anymore.
