Siebel Java Data Bean Connection Pooling
(Doc ID 1555432.1)
Last updated on DECEMBER 15, 2019
Applies to:Siebel CRM - Version 184.108.40.206 SIA  and later
Information in this document applies to any platform.
*** Checked for relevance on 24-OCT-2019 ***
Using Self Care Application's built-in JAVA and all the services from Siebel are integrated via JDB Mechanism to perform Stateless and Stateful operations.
Following are the Properties in Siebel Properties File
siebel.conmgr.txtimeout= 1800000 Milli Sec
siebel.conmgr.sesstimeout = 3600 Sec
Example: When Stateless transaction is getting called to fetch the Account data, in random occasion, the following errors are Returned to U.I From Siebel:
Yhteysvaranto on tyhjä eikä yhteyttä voitu muodostaa.(SBL-JCA-00310). SBL-JCA-00310-The connection pool is empty and no connection could be created.
Question 1: Why does this below error occurs? Is the Connection Pool Size in Siebel full?
Object Manger is Enabled in 2 Servers below are the details
MaxMTTasks - 200
Note: All Siebel Server up and running, and Max task not reached for the Siebel Component.
Question 2:The same transaction working again
For example, if QueryAccount initiated again it works. Is this happening due to Timeout Issues?
Question 3: Per Bookshelf siebel.conmgr.poolsize can be set between 2 to 500.
What is the thumb rule to Calculate this Property?
Is this Parameter setting causing this issue?
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