webMethods

 View Only

 SAP TID Confirmation Issue - SAP Adapter 10.1

Corentin MOREAU's profile image
Corentin MOREAU posted Thu July 03, 2025 04:38 AM
Hello,
 
We are encountering a blocking error when processing an inbound notification via the webMethods SAP Adapter (version 10.1 Fix14) on our webMethods Integration Server 10.15.
 
Most of the time, the SAP notifications are processed successfully without any errors.
 
However, on a sporadic basis, we encounter the following error in the IS server logs:
 
"Confirm action for nonexisting Transaction TID"
Last occurrence (server.log) :
 13:47:05 CEST [SAP.0110.0009I] (tid=1131) Inbound tRFC: Executing TID 0A498E0FDF806863CB450003 for IDOC_INBOUND_ASYNCHRONOUS from "SAP_Listener_SAP:SAP_listener"-URL-SAP
 13:47:05 CEST [SAP.0115.0001I] (tid=1131) Notification - Service "SAP_S_20510.interfaces:processZSAP" successfully executed.
 13:47:05 CEST [SAP.0110.0003I] (tid=1131) Listener - Commit 0A498E0FDF806863CB450003
 13:47:05 CEST [ISS.0024.0051I] (tid=1135) Integration Live Container UserManager getUser(), user not found --> EXPLOITATION ; (InvokeState=1705290848) (IState.string=SAPUser/null) (Session=Name: sap.rfc.Listener-"SAP_Listener_SAP:SAP_listener"-URL-SAP ID: a0194820c9b542599ca8b19ceba27f12 Date: Tue Jul 01 13:47:05 CEST 2025 User: SAPUser lastCall: 1751370425137 timeout: 0 Calls: 2 iContext(Locale): en-USValues:  >>>tenantID=null, stageID=null, WmSAP_#lockInfo=>>>BasicData:userAlias=0,userName=0<<<, accountId=null, envName=null<<<  Session fate: 0.
 13:47:05 CEST [SAP.0110.0005I] (tid=1135) Listener - Confirm 0A498E0FDF806863CB450003
 13:47:05 CEST [ISS.0098.0061I] (tid=24122) No condition matches in trigger SAP_E_20510.triggers:get_20510_messageRetourVersSAP for document Common_20510.data:MessageRetour with activation wm693192d8a-114c-4128-9733-19376358f1cf
 13:47:05 CEST [ISS.0024.0051I] (tid=1123) Integration Live Container UserManager getUser(), user not found --> EXPLOITATION ; (InvokeState=1860585066) (IState.string=SAPUser/null) (Session=Name: sap.rfc.Listener-"SAP_Listener_SAP:SAP_listener"-URL-SAP-0 ID: 057c2c598a9b4d29aa914a7f226c1c93 Date: Tue Jul 01 13:47:05 CEST 2025 User: SAPUser lastCall: 1751370425271 timeout: 0 Calls: 1 iContext(Locale): en-USValues:  >>><<<  Session fate: 0.
 13:47:05 CEST [SAP.0110.0039W] (tid=1123) Confirm action for nonexisting Transaction TID "0A498E0FDF806863CB450004"
 
When this occurs, the iDoc is not confirmed and remains in the SAP system (transaction SM58)
 
We have verified that:
 
  • No restart of the Integration Server occurred at the time of the error.
  • Network analysis showed no anomalies.
  • Connection pool settings on the RFC connection are set to:
    • Minimum Pool Size: 1
    • Maximum Pool Size: 30
  • Listener configuration is:
    • Number of Threads: 1
These settings are identical to other environments where no such issue occurs.
No related errors are visible in SAP system logs.
 
Thank you in advance for your support,
Best regards,
Corentin
Corentin MOREAU's profile image
Corentin MOREAU posted Tue July 08, 2025 07:16 AM

Still have this issue : IDoc Lost with "Confirm action for nonexisting Transaction TID"

SAP's components :

  • SAP Adapter 10.1.0.14.1192     
  • SAP_10.1_Fix14
  • JCo Version 3.1.11 (2024-11-15)
  • IDoc Library Version 3.1.3 (2023-02-24)

Latest log :

Part 1 :
2025-07-08 10:14:34 CEST [SAP.0110.0002I] (tid=1119) Listener - Create 0A498E098C00686CD3C6002B
2025-07-08 10:14:34 CEST [ISS.0024.0051I] (tid=1119) Integration Live Container UserManager getUser(), user not found --> EXPLOITATION ; (InvokeState=1523538433) (IState.string=SAPUser/null) (Session=Name: sap.rfc.Listener-"SAP_Listener_XXX:XXX_listener"-FAKEURL-server-0 ID: ba21c68e3fa84da0b01274e1a7437309 Date: Tue Jul 08 10:14:34 CEST 2025 User: SAPUser lastCall: 1751962474603 timeout: 0 Calls: 1 iContext(Locale): en-USValues:  >>><<<  Session fate: 0.
2025-07-08 10:14:34 CEST [SAP.0110.0009I] (tid=1119) Inbound tRFC: Executing TID 0A498E098C00686CD3C6002B for IDOC_INBOUND_ASYNCHRONOUS from "SAP_Listener_XXX:XXX_listener"-FAKEURL-server
2025-07-08 10:14:34 CEST [SAP.0115.0001I] (tid=1119) Notification - Service "XXX_S_20510.interfaces:processZXXXTRV_MESS_RETOUR_XXX" successfully executed.
2025-07-08 10:14:34 CEST [SAP.0110.0003I] (tid=1119) Listener - Commit 0A498E098C00686CD3C6002B
2025-07-08 10:14:34 CEST [ISS.0024.0051I] (tid=1119) Integration Live Container UserManager getUser(), user not found --> EXPLOITATION ; (InvokeState=915573234) (IState.string=SAPUser/null) (Session=Name: sap.rfc.Listener-"SAP_Listener_XXX:XXX_listener"-FAKEURL-server-0 ID: ba21c68e3fa84da0b01274e1a7437309 Date: Tue Jul 08 10:14:34 CEST 2025 User: SAPUser lastCall: 1751962474648 timeout: 0 Calls: 2 iContext(Locale): en-USValues:  >>>tenantID=null, stageID=null, WmSAP_#lockInfo=>>>BasicData:userAlias=0,userName=0<<<, accountId=null, envName=null<<<  Session fate: 0.
2025-07-08 10:14:34 CEST [SAP.0110.0005I] (tid=1119) Listener - Confirm 0A498E098C00686CD3C6002B
2025-07-08 10:14:34 CEST [ISS.0098.0061I] (tid=24101) No condition matches in trigger XXX_E_20510.triggers:get_20510_messageRetourVersXXX for document Common_20510.data:MessageRetour with activation wm61be95099-f4af-468f-8f5d-8a40052dcef4
2025-07-08 10:14:36 CEST [SAP.0110.0002I] (tid=1119) Listener - Create 0A498E094150686CD3C80003
2025-07-08 10:14:36 CEST [ISS.0024.0051I] (tid=1119) Integration Live Container UserManager getUser(), user not found --> EXPLOITATION ; (InvokeState=915573234) (IState.string=SAPUser/null) (Session=Name: sap.rfc.Listener-"SAP_Listener_XXX:XXX_listener"-FAKEURL-server-0 ID: 44ab19489d6a4dffa0d8efb78da50b59 Date: Tue Jul 08 10:14:36 CEST 2025 User: SAPUser lastCall: 1751962476768 timeout: 0 Calls: 1 iContext(Locale): en-USValues:  >>><<<  Session fate: 0.
2025-07-08 10:14:36 CEST [SAP.0110.0009I] (tid=1119) Inbound tRFC: Executing TID 0A498E094150686CD3C80003 for IDOC_INBOUND_ASYNCHRONOUS from "SAP_Listener_XXX:XXX_listener"-FAKEURL-server
2025-07-08 10:14:36 CEST [SAP.0115.0001I] (tid=1119) Notification - Service "XXX_S_0922.interfaces:processZORDERS05" successfully executed.
2025-07-08 10:14:36 CEST [SAP.0110.0003I] (tid=1119) Listener - Commit 0A498E094150686CD3C80003
2025-07-08 10:14:36 CEST [ISS.0024.0051I] (tid=1119) Integration Live Container UserManager getUser(), user not found --> EXPLOITATION ; (InvokeState=1399562965) (IState.string=SAPUser/null) (Session=Name: sap.rfc.Listener-"SAP_Listener_XXX:XXX_listener"-FAKEURL-server-0 ID: 44ab19489d6a4dffa0d8efb78da50b59 Date: Tue Jul 08 10:14:36 CEST 2025 User: SAPUser lastCall: 1751962476833 timeout: 0 Calls: 2 iContext(Locale): en-USValues:  >>>tenantID=null, stageID=null, WmSAP_#lockInfo=>>>BasicData:userAlias=0,userName=0<<<, accountId=null, envName=null<<<  Session fate: 0.
2025-07-08 10:14:36 CEST [SAP.0110.0005I] (tid=1119) Listener - Confirm 0A498E094150686CD3C80003
2025-07-08 10:14:36 CEST [ISS.0098.0061I] (tid=24101) No condition matches in trigger XXX_E_0922.triggers:get_0922_CommandeVersXXX for document Common_0922.data:Commande with activation wm639ed9a59-7f23-476f-953d-035b692bf689

Part 2 :
2025-07-08 10:25:17 CEST [SAP.0110.0002I] (tid=1119) Listener - Create 0A498E094380686CD6490003
2025-07-08 10:25:17 CEST [ISS.0024.0051I] (tid=1119) Integration Live Container UserManager getUser(), user not found --> EXPLOITATION ; (InvokeState=1399562965) (IState.string=SAPUser/null) (Session=Name: sap.rfc.Listener-"SAP_Listener_XXX:XXX_listener"-FAKEURL-server-0 ID: a02f26ad3e774a1999b4741a60edbcb5 Date: Tue Jul 08 10:25:17 CEST 2025 User: SAPUser lastCall: 1751963117758 timeout: 0 Calls: 1 iContext(Locale): en-USValues:  >>><<<  Session fate: 0.
2025-07-08 10:25:17 CEST [SAP.0110.0009I] (tid=1119) Inbound tRFC: Executing TID 0A498E094380686CD6490003 for IDOC_INBOUND_ASYNCHRONOUS from "SAP_Listener_XXX:XXX_listener"-FAKEURL-server
2025-07-08 10:25:17 CEST [SAP.0115.0001I] (tid=1119) Notification - Service "XXX_S_0922.interfaces:processZORDERS05" successfully executed.
2025-07-08 10:25:17 CEST [SAP.0110.0003I] (tid=1119) Listener - Commit 0A498E094380686CD6490003
2025-07-08 10:25:17 CEST [ISS.0024.0051I] (tid=1119) Integration Live Container UserManager getUser(), user not found --> EXPLOITATION ; (InvokeState=1130457080) (IState.string=SAPUser/null) (Session=Name: sap.rfc.Listener-"SAP_Listener_XXX:XXX_listener"-FAKEURL-server-0 ID: a02f26ad3e774a1999b4741a60edbcb5 Date: Tue Jul 08 10:25:17 CEST 2025 User: SAPUser lastCall: 1751963117820 timeout: 0 Calls: 2 iContext(Locale): en-USValues:  >>>tenantID=null, stageID=null, WmSAP_#lockInfo=>>>BasicData:userAlias=0,userName=0<<<, accountId=null, envName=null<<<  Session fate: 0.
2025-07-08 10:25:17 CEST [SAP.0110.0005I] (tid=1119) Listener - Confirm 0A498E094380686CD6490003
2025-07-08 10:25:17 CEST [ISS.0098.0061I] (tid=24101) No condition matches in trigger XXX_E_0922.triggers:get_0922_CommandeVersXXX for document Common_0922.data:Commande with activation wm65ef06186-03c3-4fcc-b93b-41b1c4f2686c
2025-07-08 10:25:17 CEST [ISS.0024.0051I] (tid=1119) Integration Live Container UserManager getUser(), user not found --> EXPLOITATION ; (InvokeState=1130457080) (IState.string=SAPUser/null) (Session=Name: sap.rfc.Listener-"SAP_Listener_XXX:XXX_listener"-FAKEURL-server-0 ID: f08cd52feb674c66b67ca982de0338ea Date: Tue Jul 08 10:25:17 CEST 2025 User: SAPUser lastCall: 1751963117946 timeout: 0 Calls: 1 iContext(Locale): en-USValues:  >>><<<  Session fate: 0.
2025-07-08 10:25:17 CEST [SAP.0110.0039W] (tid=1119) Confirm action for nonexisting Transaction TID "0A498E094380686CD6490004"
2025-07-08 10:25:41 CEST [SAP.0110.0021I] (tid=24100) TransactionManager: Deleting transactions: 0 deleted.
2025-07-08 10:25:41 CEST [SAP.0110.0021I] (tid=24100) TransactionManager: Deleting transactions: 0 deleted.
2025-07-08 10:25:41 CEST [SAP.0110.0021I] (tid=24100) TransactionManager: Deleting transactions: 0 deleted.

This seems to occur when multiple IDocs are received at the same time via the SAP Adapter. The IDoc associated with the TID in the error message is lost and never processed, which is a critical issue for our business processes (log part 2)

However, we are also able to receive and process several IDocs in parallel without any problem, which makes the issue intermittent and hard to isolate (log part 1).
Notice that "...0003" TID was successfully processed and confirmed, but then "...0004" TID failed with the warning above and no creation or execution was logged for this TID

Let me know if more traces or configuration exports are needed.
Thank you in advance,

Best regards,

Corentin

Related Content