Siebel Business Process & Functionality (MOSC)

MOSC Banner

Siebel Application Timeout Settings

edited Nov 4, 2014 6:28PM in Siebel Business Process & Functionality (MOSC) 5 commentsAnswered

Hello expert,

when we launch the application it is throwing server busy error message. This is happening sporadically.


We followed Siebel Application Timeout Setting Guideline ( Doc ID 838460.1 . to implement the session time out parameter for each layer, but still we are getting the server busy  error message .


Here is the parameter which we implemented, please let us whether we have to modify


SISNAPI connection maximum idlE = 3500

Appserver F5 : 3600

Web server eapps.cfg : 3400

Web server F5 : 3900

Firewall: TCP timeouts for inactive sessions is 2 hour i.e. 7200 Seconds

Note : Our Siebel Environment has 2 gateway servers(Red had clustered) 4 App server with F5 Load balancing and d Finally 4 Web server with F5 load balancing .

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

SBL Business Process Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center