APAR status
Closed as program error.
Error description
<div>If an SAPInput node rolls back a transaction because an exception was thrown in the message flow and assured delivery is enabled then the following exception may be observed in the JCo traces:</div><div> </div><div>Info: >Thu Oct 27 11:41:03,347< [JCoRFC] onConfirm failed:</div><div>com.sap.conn.jco.JCoRuntimeException: (1000) null: com.ibm.j2ca.extension.utils.persistencestore.exception.EventNot FoundException</div><div> at com.ibm.broker.adapter.persistentstore.MbPersistentEventStoreSha red.getEventStatus(MbPersistentEventStoreShared.java:84)</div><d iv> at com.ibm.j2ca.extension.utils.persistencestore.EventPersistence.g etEventStatus(EventPersistence.java:279)</div><div> at com.ibm.j2ca.sap.inbound.eventrecovery.EventRecoveryManager.getE ventStatus(EventRecoveryManager.java:55)</div><div> at com.ibm.j2ca.sap.inbound.SapTrfcFunctionHandler.confirmTID(SapTr fcFunctionHandler.java:119)</div><div> at com.ibm.j2ca.sap.ext.SapJCoServerHandlerFactory$SapGenericServer Handler.confirmTID(SapJCoServerHandlerFactory.java:319)</div><di v> at com.sap.conn.jco.rt.AbstractServerWorker.onConfirmTID(AbstractSe rverWorker.java:299)</div><div> at com.sap.conn.jco.rt.AbstractServerConnection.handletRfcConfirm(A bstractServerConnection.java:1441)</div><div> </div><div>This is caused by the persistent event store failing to find a transaction in the persistent store when SAP issues confirmTID to indicate that transactional processing for this IDOC has been completed. The reason for this is that ACE is looking in the MQ queues for the event, however in the rollback case an optimization means that this transaction is held only in memory.</div><div> </div><div>Note that this has no effect on the transaction in SAP since this will already have been rolled back, the only symptom is the spurious error in the JCo traces. </div>
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM App Connect Enterprise version 12 or higher using the SAPInput Node with Assured Delivery Enabled Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: <div>If an SAPInput node rolls back a transaction because an exception was thrown in the message flow and assured delivery is enabled then the following exception may be observed in the JCo traces:</div><div> </div><div>Info: >Thu Oct 27 11:41:03,347< [JCoRFC] onConfirm failed:</div><div>com.sap.conn.jco.JCoRuntimeException: (1000) null: com.ibm.j2ca.extension.utils.persistencestore.exception.EventNot FoundException</div><div> at com.ibm.broker.adapter.persistentstore.MbPersistentEventStoreSha red.getEventStatus(MbPersistentEventStoreShared.java:84)</div><d iv> at com.ibm.j2ca.extension.utils.persistencestore.EventPersistence.g etEventStatus(EventPersistence.java:279)</div><div> at com.ibm.j2ca.sap.inbound.eventrecovery.EventRecoveryManager.getE ventStatus(EventRecoveryManager.java:55)</div><div> at com.ibm.j2ca.sap.inbound.SapTrfcFunctionHandler.confirmTID(SapTr fcFunctionHandler.java:119)</div><div> at com.ibm.j2ca.sap.ext.SapJCoServerHandlerFactory$SapGenericServer Handler.confirmTID(SapJCoServerHandlerFactory.java:319)</div><di v> at com.sap.conn.jco.rt.AbstractServerWorker.onConfirmTID(AbstractSe rverWorker.java:299)</div><div> at com.sap.conn.jco.rt.AbstractServerConnection.handletRfcConfirm(A bstractServerConnection.java:1441)</div><div> </div><div>This is caused by the persistent event store failing to find a transaction in the persistent store when SAP issues confirmTID to indicate that transactional processing for this IDOC has been completed. The reason for this is that ACE is looking in the MQ queues for the event, however in the rollback case an optimization means that this transaction is held only in memory.</div><div> </div><div>Note that this has no effect on the transaction in SAP since this will already have been rolled back, the only symptom is the spurious error in the JCo traces. </div>
Problem conclusion
The exception is no longer emitted in the JCO Traces under these circumstances --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v12.0 12.0.12.8 v13.0 13.0.2.0 The latest available maintenance can be obtained from: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If the maintenance level is not yet available,information on its planned availability can be found on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT42902
Reported component name
APP CONNECT ENT
Reported component ID
5724J0550
Reported release
B00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-01-16
Closed date
2024-11-04
Last modified date
2024-11-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
APP CONNECT ENT
Fixed component ID
5724J0550
Applicable component levels
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]
Document Information
Modified date:
04 November 2024