Open glassfishrobot opened 12 years ago
@glassfishrobot Commented Reported by @nigeldeakin
@glassfishrobot Commented @nigeldeakin said: A brief investigation suggests that when the message is sent in the second transaction, the packet that is sent contains the transactionID from the first transaction. Since this transaction was committed this causes the broker to return an "unknown transaction" error.
The cause seems to be that when a message is sent, the transactionid is copied from the DirectSession to the Packet being sent. However this transactionid is not re-initialised when the second transaction is started.
@glassfishrobot Commented This issue was imported from java.net JIRA MQ-145
I have a session bean which uses bean-managed transactions as follows: (The full bean is pasted below)
This works fine in GlassFish 3.1.2 with a LOCAL broker. However if the broker is embedded, the second call to send() throws a JMSException. The exception is:
The full bean is:
Affected Versions
[4.5.2]