JCA Adapter Issue – Connection Lock When Using Two JCA Connection Factories and One Becomes Full
(Doc ID 2464884.1)
Last updated on SEPTEMBER 24, 2019
Applies to:Siebel CRM - Version 16.9 [IP2016] and later
Information in this document applies to any platform.
Object Managers encountering a connection lock when MaxConnections set to 20 for both factories and define 2 different ConnectString that point to 2 different Object managers and set MaxTasks to 20 for the 2 different .
The problem is observed when only one of the factories pools (no matter which one) is full and the IBM Pool Manager starts to queue incoming getConnection() Requests.
1.Define 2 HttpServlets written based on respectively vanilla BS "EAI Siebel Adapter" and "EAI File Transport"
2.Define 2 factories inside the installed Siebel Resource Adapter
3.Set MaxConnections to 20 for both factories and define 2 different ConnectString that point to 2 different Object managers
4.Set MaxTasks to 20 for the 2 different Object Managers
5.Try to start 21 parallel threads to connect to HttpServlet1 (All threads should be blocked) and will be released once the the thread 21 reaches the ConnectionTimeout set for the factory.
6.Try to connect to httpservlet2 during that time, the same behavior is observed although the factory pool used by httpservlet2 is empty.
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