Siebel EAI Tasks Created By JCA (Siebel Resource Adapter) From Tibco Are Not Closed Even After The Transaction Has Completed Processing Successfully (Doc ID 2882487.1)

Last updated on APRIL 04, 2025

Applies to:

Symptoms

Siebel application has been configured to integrate with Tibco using Siebel Resource Adapter (JCA).

Tibco is opening three sessions and these sessions are never closed out.

When looking into the log files, the log file shows that the session is not idle, so Tibco continues to use the same EAI session/task.

However, this was not the intended behaviour.  Customer intended for/desired for the Siebel EAI session to close out as soon as the request sent by Tibco is processed and completed.  Then, when a new request is sent from Tibco, the desire is to create/open a new EAI session/task on the Siebel application side.

The issue can be replicated with the following steps:
1. Tibco sends requests to siebel
2. It opens three sessions
3. After request is completed the sessions/tasks remains open and reused for new tasks and never closed

Cause

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