Managing MQ/TIBCO Connections And JMS Connection Leaks
(Doc ID 983912.1)
Last updated on MAY 12, 2021
Applies to:Siebel CRM - Version 7.7.1  to 19.2 [Release V7 to V17]
Information in this document applies to any platform.
This documentation addresses:
1. Connections leaks and what are the recommended actions to be performed when this happens.
Connections should not grow indefinitely.
2. Configuration steps required to make Siebel JMS Receiver to close and re-connect to JMS Queue atter a message receipt.
This approach can be used to efficiently manage connection distributed Queues of Oracle WebLogicServer or to re-set connection pool issues of encountered by other Messaging systems (such as IBM WebSphere MQ, TIBCO EMS etc ).
The issue can be replicated with the following steps:
1. Log in to Call Center and go to Site Map -> Administration - business Services -> Simulator.
2. Simulate EAI JMS Transport Send.
3. Go to TIBCO Admin and run the command : show connections user=anonymous
This will show one connection with zero sessions ( ghost connections ).
4. Log off from Siebel thin client.
5. Log back in -> Simulate EAI JMS Transport again and re-check the connections for anonymous.
6. There should be 2 now -> Repeat
Every time a log off / log in happens, plus running the transport, a new connection is created and never terminated.
This means that connections are leaking.
Sometimes, this can lead to 'EAI JMS Transport' opening an excessive number of connections and error "java.lang.OutOfMemoryError: Java heap space".
List of errors
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!