My Oracle Support Banner

JMS Connections Remain Established Even Though Timeout Is Reached (Doc ID 2896310.1)

Last updated on APRIL 01, 2024

Applies to:

Siebel CRM - Version 22.3 and later
Information in this document applies to any platform.

Symptoms

After configuring JMS via the JAVA 64 profile, tasks eventually reach 200, then the JMS receivers stop working, although a timeout is thrown for the tasks.

In the JMS Listener component log, we can see the following being logged every 3 minutes:

The issue can be reproduced at will with the following steps:
1. Upgrade Siebel from IP16 to 22.3.
2. Deploy a JAVA 64 profile to be used for JMS connections.
3. Start a JMS integration with Tibco to pull messages from the queue.
4. Notice that the number of tasks keeps rising, with no JMS tasks being terminated or reused.

Changes

 Configuring a JAVA 64 profile to use JMS in order to communicate with Tibco external system.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


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