When periodic crash recovery runs with Tibco remote broker and rollback is expected then the log contains "java.lang.Throwable: Lock owned during cleanup" warning [1]. The server log should be clean for crash recovery. This seems does not influence the results of the test (functionality of the recovery). [1] WARN [org.jboss.resource.adapter.jms.JmsManagedConnection] (Periodic Recovery) Lock owned during cleanup: java.lang.Throwable: Lock owned during cleanup at java.lang.Object.wait(Native Method) [rt.jar:1.7.0_45] at java.lang.Object.wait(Object.java:503) [rt.jar:1.7.0_45] at com.tibco.tibjms.TibjmsxLink.sendRequest(TibjmsxLink.java:359) [tibjms.jar:6.3.0] at com.tibco.tibjms.TibjmsXAResource.rollbackTx(TibjmsXAResource.java:645) [tibjms.jar:6.3.0] at com.tibco.tibjms.TibjmsXAResource._rollback(TibjmsXAResource.java:455) [tibjms.jar:6.3.0] at com.tibco.tibjms.TibjmsXAResource.rollback(TibjmsXAResource.java:444) [tibjms.jar:6.3.0] at org.jboss.resource.adapter.jms.JmsXAResource.rollback(JmsXAResource.java:94) at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.rollback(XAResourceWrapperImpl.java:186) at com.arjuna.ats.internal.jta.resources.jts.orbspecific.XAResourceRecord.rollback(XAResourceRecord.java:377) [jbossjts-jacorb-4.17.12.Final-redhat-1.jar:4.17.12.Final-redhat-1] at com.arjuna.ArjunaOTS.OTSAbstractRecordPOA._invoke(OTSAbstractRecordPOA.java:213) [jbossjts-jacorb-4.17.12.Final-redhat-1.jar:4.17.12.Final-redhat-1] at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:306) [jacorb-2.3.2-redhat-4.jar:2.3.2-redhat-4] at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:626) [jacorb-2.3.2-redhat-4.jar:2.3.2-redhat-4] at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:769) [jacorb-2.3.2-redhat-4.jar:2.3.2-redhat-4]
I forgot to mention that this happens with transactions set to jts.
This may not be the cause but is it possible that rollback has been called twice? In the scenario where we get to call rollback on the XAR (e.g. immediately pre crash) but then crash we will call it again on recovery.
Hi, I've checked the proceeding of the recovery and it seems that Tom is right. The second call of the rollback on the XAR (arjuna 4.17.12.Final call from XAResourceRecord, l:377) causes the warning being written to the server log. Just a note: the second call of the rollback on the same XAR is OK. It's in accordance with OTS specification (discussed on this bz https://bugzilla.redhat.com/show_bug.cgi?id=988724#c2). Ondra
I have edited this BZ ticket's release notes entry. Please review the text and confirm whether or not it is accurate.
The text is ok. I just added the abbreviation jts to the text for this being more obvious what does it mean. It's because the abbreviation jts is used as configuration parameter in transaction subsystem.
Hi, This issue has not been touched in many months. Is it intended to be resolved in product or can we close it? Tom