javax.ejb.EJBException: Transaction aborted; nested exception is: javax.transaction.RollbackException;|MDB00037: [backend-ear-0.0.0.1-SNAPSHOT:MessageProcessor]: Message-driven bean invocation ex ception: [javax.ejb.EJBException: Transaction aborted; nested exception is: javax.transaction.RollbackException]|#] We suspected that the broker was removing the messages even before the acknowledgement is received from the MDB due to the TTL being set for some types of messages. Hence, we changed the TTL value to 0. However, even after making the TTL to 0, we still see that the exceptions are still being thrown [#|2010-08-05T11:10:34.136+0200|WARNING|sun-glassfish-comms-server1.5|javax.jms|_ThreadID=435;_ThreadName=p: thread-pool-1; w: 109;_RequestID=c71cd362-db29-413b-bcd0-ffeb7a864865;|[I500]: Caught JVM Exception: com.sun.messaging.jms.JMSException: [ACKNOWLEDGE_REPLY(25)] [C4036]: A broker error occurred. :[409] [B1290]: Transaction acknowledgement could not be processed because message 2720528-192.168.0.4(c7:69:53:86:9e:d4)-59781-1280998929518[[consumer:2274927222597296128, type=NONE]:[consumer:0, type=CLIENT_ACKNOWLEDGE]]TUID=2274927222650419200 reference is gone user=guest, broker=localhost:37676(43191)|#] [#|2010-08-05T11:10:34.136+0200|WARNING|sun-glassfish-comms-server1.5|javax.enterprise.system.stream.err|_ThreadID=435;_ThreadName=p: thread-pool-1; w: 109;_RequestID=c71cd362-db29-413b-bcd0-ffeb7a864865;| MQRA:OMR:run:JMSException on message acknowledgement:Rolling back if in txn|#] [#|2010-08-05T11:10:34.137+0200|WARNING|sun-glassfish-comms-server1.5|javax.enterprise.system.stream.err|_ThreadID=435;_ThreadName=p: thread-pool-1; w: 109;_RequestID=c71cd362-db29-413b-bcd0-ffeb7a864865;| com.sun.messaging.jms.JMSException: [ACKNOWLEDGE_REPLY(25)] [C4036]: A broker error occurred. :[409] [B1290]: Transaction acknowledgement could not be processed because message 2720528-192.168.0.4(c7:69:53:86:9e:d4)-59781-1280998929518[[consumer:2274927222597296128, type=NONE]:[consumer:0, type=CLIENT_ACKNOWLEDGE]]TUID=2274927222650419200 reference is gone user=guest, broker=localhost:37676(43191)

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

Do you know how to solve this issue? Write a tip to help other users and build your expert profile.

Solutions on the web

via Oracle Community by 392 Guest, 1 year ago
, even after making the TTL to 0, we still see that the exceptions are still being thrown [#|2010-08-05T11:10:34.136+0200|WARNING|sun-glassfish-comms-server1.5|javax.jms|_ThreadID=435;_ThreadName=p: thread-pool-1; w: 109;_RequestID=c71cd362-db29-413b
via Oracle Community by 843810, 4 months ago
received a parameter that is not valid. user=admin, broker=sea-ax0073:20076(58591) com.sun.messaging.jms.JMSException: [SEND_REPLY(9)] [C4036]: A broker error occurred. :[500] transaction failed: java.io.IOException: A system call received a parameter that is not valid. user=admin, broker=sea-ax0073:20076(58591)
javax.ejb.EJBException: Transaction aborted; nested exception is: javax.transaction.RollbackException;|MDB00037: [backend-ear-0.0.0.1-SNAPSHOT:MessageProcessor]: Message-driven bean invocation ex ception: [javax.ejb.EJBException: Transaction aborted; nested exception is: javax.transaction.RollbackException]|#] We suspected that the broker was removing the messages even before the acknowledgement is received from the MDB due to the TTL being set for some types of messages. Hence, we changed the TTL value to 0. However, even after making the TTL to 0, we still see that the exceptions are still being thrown [#|2010-08-05T11:10:34.136+0200|WARNING|sun-glassfish-comms-server1.5|javax.jms|_ThreadID=435;_ThreadName=p: thread-pool-1; w: 109;_RequestID=c71cd362-db29-413b-bcd0-ffeb7a864865;|[I500]: Caught JVM Exception: com.sun.messaging.jms.JMSException: [ACKNOWLEDGE_REPLY(25)] [C4036]: A broker error occurred. :[409] [B1290]: Transaction acknowledgement could not be processed because message 2720528-192.168.0.4(c7:69:53:86:9e:d4)-59781-1280998929518[[consumer:2274927222597296128, type=NONE]:[consumer:0, type=CLIENT_ACKNOWLEDGE]]TUID=2274927222650419200 reference is gone user=guest, broker=localhost:37676(43191)|#] [#|2010-08-05T11:10:34.136+0200|WARNING|sun-glassfish-comms-server1.5|javax.enterprise.system.stream.err|_ThreadID=435;_ThreadName=p: thread-pool-1; w: 109;_RequestID=c71cd362-db29-413b-bcd0-ffeb7a864865;| MQRA:OMR:run:JMSException on message acknowledgement:Rolling back if in txn|#] [#|2010-08-05T11:10:34.137+0200|WARNING|sun-glassfish-comms-server1.5|javax.enterprise.system.stream.err|_ThreadID=435;_ThreadName=p: thread-pool-1; w: 109;_RequestID=c71cd362-db29-413b-bcd0-ffeb7a864865;| com.sun.messaging.jms.JMSException: [ACKNOWLEDGE_REPLY(25)] [C4036]: A broker error occurred. :[409] [B1290]: Transaction acknowledgement could not be processed because message 2720528-192.168.0.4(c7:69:53:86:9e:d4)-59781-1280998929518[[consumer:2274927222597296128, type=NONE]:[consumer:0, type=CLIENT_ACKNOWLEDGE]]TUID=2274927222650419200 reference is gone user=guest, broker=localhost:37676(43191)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.throwServerErrorException(ProtocolHandler.java:4003)

Users with the same issue

Samebug visitor profile picture
Unknown user
2 times, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.