Troubleshooting
Problem
In SAP outbound scenarios for ALE and BAPI interfaces, the adapter closed the connection before the commit is executed properly and the transactions changed their mode from "stateful" to "stateless".This is being addressed in APAR JR37273.
Symptom
Commits not being effective.
Environment
WebSphere Adapter for SAP 7.0.0.1, WebSphere Process Server 7.0.0.2/ WebSphere Enterprise Service Bus 7.0.0.2. Problem emerged on Linux and Windows systems.
Diagnosing The Problem
Several observations can be made to diagnose the problem:
- After a certain idle time on the SAP system (for example after 15 minutes), a disconnect ("timeout") of the adapter can be observed in the logs. In the SAPGUI transaction SMGW, it can be seen whether the connection was lost after a certain idle time.
- On Adapter side in the traces, the first thread is working properly and the COMMIT issued correctly. The subsequent thread contains a "connection handle closed" before invoking the COMMIT.
- In the JCo, RFC and Adapter trace it can be seen that the destination changes from "stateful" to "null" after a certain time.
[JCoAPI] ... (state: destination = STATEFUL, general = null, default = STATELESS) [JCoAPI] ... (state: destination = null, general = null, default = STATELESS)
In summary, after a connection turned stateless following the connection timeout, the commits will be not be effective on the SAP system.
Resolving The Problem
The problem was addressed with APAR JR37273.
The JCo runtime calls the JCoTimeChecker to see if the connection is idle and destroys it. Once the connection is destroyed, the destination state goes from STATEFUL into STATELESS mode and the updates are not being effective on SAP system side.
Please check the latest Fix Packs available:
Recommended fixes for WebSphere Adapters
If the fix is not yet released, please contact IBM Support.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21443342