SAP Adapter CPU usage stays at 50% after startingup

SAP Adapter CPU usage stays at 50% after startingup

book

Article ID: KB0083526

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks Plug-in for SAP Solutions 7.x

Description

After startingup the SAP Adapter, the adapter process's CPU usage stays at 50% when there are more than 50 inbound services defined in one SAP Adapter configuration, and service transport is JMS.

Issue/Introduction

SAP Adapter CPU usage stays at 50% after startingup.

Environment

ALL

Resolution

There is a limitation on the Adapter SDK that the total consumer in one JMS session should be no more than 50. If the Adapter implements a multiplethreaded message dispatcher, a JMS session with more than 50 consumers would cause the CPU usage staying at 50%. SAP Adapter is a multithreaded implementation so this limitation is applicable to the SAP Adapter. To resolve this issue, keep the total number of inbound services on the JMS transport to less than 50 in one SAP Adapter configuration,