We are running into a problem with JMS I have not seen before.
It looks like the message is produced, and then the next message in the lifecycle is Retry Exceeded (retry is set to 0 for this queue.)
The MDB does not ever get called.
In a local Weblogic environment, the messages are delivered as expected. However, in the clustered environment we see the above behavior.
Any suggestions what to look for?