Back to bug 1023193

Who When What Removed Added
Ondrej Chaloupka 2013-10-25 05:39:17 UTC CC tom.jenkinson
Ondrej Chaloupka 2013-11-29 14:15:55 UTC Doc Text Cause:
By OTS specification (when transaction manager is set to be run on jts) the periodic recovery calls rollback for the same XID twice. The generic jms adapter incorrectly handles the second call of the rollback for the same xid and warnings are put in the log.

Consequence:
The log is messed with warning messages. This does not cause any problem in functionality of crash recovery. It just generates warning messages to server log.

Fix:

Result:
User needs to be prepared to see the warning messages in the log.
Russell Dickenson 2013-12-02 00:29:30 UTC Doc Text Cause:
By OTS specification (when transaction manager is set to be run on jts) the periodic recovery calls rollback for the same XID twice. The generic jms adapter incorrectly handles the second call of the rollback for the same xid and warnings are put in the log.

Consequence:
The log is messed with warning messages. This does not cause any problem in functionality of crash recovery. It just generates warning messages to server log.

Fix:

Result:
User needs to be prepared to see the warning messages in the log. 		A minor issue with periodic recovery has been identified, where warning messages beginning with the following text are logged.

----
WARN [org.jboss.resource.adapter.jms.JmsManagedConnection] (Periodic Recovery) Lock owned during cleanup: java.lang.Throwable: Lock owned during cleanup
----

The underlying cause of the issue is that the generic JMS adapter mishandles the second periodic recovery call. In accordance with the Object Transaction Service specification, when the transaction manager is set to be run on the Java Transaction Service the periodic recovery calls rollback for the same XID twice. The issue is that the generic JMS adapter incorrectly handles the second call of the rollback for the same XID and the above warnings are logged. Note that despite the warning messages, recovery occurs correctly.
Doc Type Bug Fix Known Issue
Ondrej Chaloupka 2013-12-02 08:05:13 UTC Doc Text A minor issue with periodic recovery has been identified, where warning messages beginning with the following text are logged.

----
WARN [org.jboss.resource.adapter.jms.JmsManagedConnection] (Periodic Recovery) Lock owned during cleanup: java.lang.Throwable: Lock owned during cleanup
----

The underlying cause of the issue is that the generic JMS adapter mishandles the second periodic recovery call. In accordance with the Object Transaction Service specification, when the transaction manager is set to be run on the Java Transaction Service the periodic recovery calls rollback for the same XID twice. The issue is that the generic JMS adapter incorrectly handles the second call of the rollback for the same XID and the above warnings are logged. Note that despite the warning messages, recovery occurs correctly. 		A minor issue with periodic recovery has been identified, where warning messages beginning with the following text are logged.

----
WARN [org.jboss.resource.adapter.jms.JmsManagedConnection] (Periodic Recovery) Lock owned during cleanup: java.lang.Throwable: Lock owned during cleanup
----

The underlying cause of the issue is that the generic JMS adapter mishandles the second periodic recovery call. In accordance with the Object Transaction Service specification, when the transaction manager is set to be run on the Java Transaction Service (jts) the periodic recovery calls rollback for the same XID twice. The issue is that the generic JMS adapter incorrectly handles the second call of the rollback for the same XID and the above warnings are logged. Note that despite the warning messages, recovery occurs correctly.
Russell Dickenson 2013-12-03 13:41:22 UTC Doc Text A minor issue with periodic recovery has been identified, where warning messages beginning with the following text are logged.

----
WARN [org.jboss.resource.adapter.jms.JmsManagedConnection] (Periodic Recovery) Lock owned during cleanup: java.lang.Throwable: Lock owned during cleanup
----

The underlying cause of the issue is that the generic JMS adapter mishandles the second periodic recovery call. In accordance with the Object Transaction Service specification, when the transaction manager is set to be run on the Java Transaction Service (jts) the periodic recovery calls rollback for the same XID twice. The issue is that the generic JMS adapter incorrectly handles the second call of the rollback for the same XID and the above warnings are logged. Note that despite the warning messages, recovery occurs correctly. 		A minor issue with periodic recovery has been identified, where warning messages beginning with the following text are logged.

----
WARN [org.jboss.resource.adapter.jms.JmsManagedConnection] (Periodic Recovery) Lock owned during cleanup: java.lang.Throwable: Lock owned during cleanup
----

The underlying cause of the issue is that the generic JMS adapter mishandles the second periodic recovery call. In accordance with the Object Transaction Service specification, when the transaction manager is set to be run on the Java Transaction Service (JTS) the periodic recovery calls rollback for the same XID twice. The issue is that the generic JMS adapter incorrectly handles the second call of the rollback for the same XID and the above warnings are logged. Note that despite the warning messages, recovery occurs correctly.
Miroslav Novak 2013-12-12 10:18:12 UTC CC mnovak
QA Contact vrastsel mnovak
mark yarborough 2014-10-26 16:18:13 UTC Keywords Question
Target Release --- EAP 6.4.0
mark yarborough 2014-10-26 17:11:00 UTC Keywords Question
Jeff Mesnil 2014-10-27 08:27:48 UTC Component JCA JMS
Martin Svehla 2014-11-10 11:36:54 UTC CC msvehla
Russell Dickenson 2017-10-10 00:08:26 UTC Docs Contact rdickens
Jan Kurik 2019-08-19 12:45:10 UTC Status NEW CLOSED
Resolution --- EOL
Last Closed 2019-08-19 12:45:10 UTC

Back to bug 1023193