Thanks artnaseef, for pointing me in the right direction.The issue was mainly
because it was running under JTA transaction, and hence the consumers were
not releasing the connection. So after around 50-100 polls, all the
connections were exhausted.
I was able to fix it by making
TransactionSuppor
Thanks for posting your findings.
That's an interesting fix given the fact that the JMS spec states that a JMS
connection created within a JTA transaction participates in that transaction
automatically (although I'm sure it's fine for a provider to allow a means
to pull it out of the transaction).
Are you hitting your catch block? Add logging before you re-throw to find
out.
Also, a thread dump could help determine if you're stuck in a blocking call
or bombing out early, though it won't tell you why you bombed out (that's
what the logging in the catch block is for).
What are the queue sta
So there are a few concerns with the code.
First off, to your question of consumption stopping - based on the fact that
the code uses ActiveMQResourceAdapter, I assume this is running in the
context of a JTA Transaction. If so, all operations are transacted, and the
client acknowledge mode is ign
