Description:
When the SAP adapter is configured for JMS transport, the processing rate decrease with the increase in number of Adapter service endpoints configured on a single JMS Session. The performance further decreases as the size of the message, no. of services in adapter instance and the no. of threads configured for the adapter increases.

Symptoms
========
When adapter is configured for JMS transport, the performance of the adapter is low if:

1) Adapter had multiple services under one instance.
2) All the Adapter service endpoints are under a single JMS session.
3) Max connections are set to be greater than 1.
4) One of the services is handling high load.

Impact
======
The performance of the adapter is poor when the adr3.connections is set as greater than 1.The adapter executes at a very good rate when the adr3.maxconnections is set as 1.The performance of the adapter is drastically low when the no. of connections is increased.

Cause
=====
We are still investigating the cause of this issue with our Adapter Engineering and Adapter SDK team.

Workaround
==========
Any one of the below workarounds can be applied:
1. Create separate JMS sessions for each of the Adapter endpoints.
2. Separate out services handling high load or large messages.
3. If there are multiple services in an adapter instance, split and distribute the services to multiple instances.
4. Use RV Transport
5. Use single threaded adapter.

Resolution
=========
SDK and SAP Adapter Engineering is currently investigating possible ways to resolve this issue.
Symptoms:

Cause:

When the SAP adapter is used with JMS transport, the processing rate decrease with the increase in number of services configured on a single JMS Session.