IBM Support

WebSphere Adapter for SAP Software V7.0 uses the same thread name for all listeners with JCO3

Troubleshooting


Problem

With the new SAP JCO3 (sapjco3.jar) version, WebSphere Adapter for SAP Software version 7.0 uses the same thread name for all listeners (RFC SERVERs) which are created.

Symptom

While running WebSphere Adapter for SAP Software V7.0 inbound module in runtime, the thread name that is used for each listener (RFC SERVER) is the same. This is only applicable for ALE and BAPI inbound interfaces with SAP JCO3 version jar. Below is an example of the Adapter trace information that will be generated:

[5/8/09 12:24:14:046 CST] 0000004a SAPRA001 I SAPJcoServerStatusHandler traceServerState ALE Event Listener : JCO_SERVER , State is : ALIVE
[5/8/09 12:24:14:046 CST] 0000004a SAPRA001 I SAPJcoServerStatusHandler traceServerState ALE Event Listener : JCO_SERVER , State is : STARTED
[5/8/09 12:24:14:062 CST] 0000004a SAPRA001 I SAPJcoServerStatusHandler serverStateChangeOccurred Server thread JCO_SERVER changed state from [ STARTED ] to [ STARTED ]

Cause

Currently with SAP JCO3 version, the listener life cycle management is handled by the JCO3 jar itself. Adapter does not handle the RFC server life cycle.

Resolving The Problem

This problem does not affect any behavior of the Adapter . WebSphere Adapter for SAP Software V7.0 with JCO3 jar supports all the features and behaviors which are supported by earlier versions with JCO 2.1.8 version.

[{"Product":{"code":"SSMKUK","label":"WebSphere Adapters Family"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Adapter for SAP","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF012","label":"IBM i"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
15 June 2018

UID

swg21388273

Page Feedback