Siebel Java Data Bean Connection Pooling
(Doc ID 1555432.1)
Last updated on APRIL 30, 2018
Applies to:Siebel CRM - Version 188.8.131.52 SIA  and later
Information in this document applies to any platform.
Reviewed for relevance "6-APR-2-16".
We are using Self Care Application's built in JAVA and all the Services from Siebel is integrated via JDB Mechanism to Perform Stateless and State full Operations.
Following are the Properties in Siebel Properties File
siebel.conmgr.poolsize = 27
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 below Error are Returned to U.I Form 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 this below Error Occurs does the Connection Pool Size in Siebel is Full?
Object Manger is Enabled in 2 Servers below are the details
MinSharedDbConns 199, MinTrxDbConns 10
MaxMTTasks - 200
Note: All Siebel Server were up and running and Max task is also not reached for the Siebel Component.
Question 2:The same transaction is working again ex:if QueryAccount initiated again it is working,so we assume it is not happening due to Time Out Issues.Please Confirm?
Question 3: In Bookshelf siebel.conmgr.poolsize can be set between 2 to 500.Please Let me know thumb rule Calculate the this Properties.Does this Parameter Setting is 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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|