Siebel JMS Receiver - Option to Limit the Number of Oracle Database Connections Opened for JMS - Direct AQ Integrations (Doc ID 3001861.1)

Last updated on APRIL 25, 2024

Applies to:

Symptoms

Actual behavior:
While testing Siebel JMS integration, it was observed that JMS Receiver components (standard or custom created ones) are opening new connections to Oracle AQ Database on all message polling attempts.
This results in higher CPU usage on the Oracle Database machine (up to ~50% of overall CPU for these repeated connections).

Expected behavior:
To avoid this effects on the Database side, ideally those connections should be reused, to avoid the overhead of closing and re-opening those each and every time.
On an Exa CC / Exa CS implementation for example, that higher CPU usage can impact other apps / databases running on same server as well.


The steps to replicate this at will in that specific environment are:

1. Start the JMSReceiver component;
2. Monitor the connections in JBS/JMS logs and on the Database side (using Audit feature for instance);
3. See those sessions open / closed at every polling attempt off the queue.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.