Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Siebel Business Process & Functionality (MOSC)

Failure on Communication Server

May 29, 2013 10:41AM edited May 29, 2013 10:51AM in Siebel Business Process & Functionality (MOSC) 3 commentsAnswered ✓

On Saturday May 28th, we had a production’s problem.Most of the CallCenter users were experimenting great slowness on their workstation. After some investigation, we found out that one of the 4 communication server was not responsive, as confirmed by the srvrmgr output below.

SRVR_COMFR3 | |NGIMRCPROD3|D:\sba81\siebsrvr|9624 |ExÃ©cution en cours|
SRVR_COMFR4 | |NGIMRCPROD4|D:\sba81\siebsrvr|3148 |ExÃ©cution en cours|
SRVR_COMFR2 | |ngimrcprod2|D:\sba81\siebsrvr|2232 |ExÃ©cution en cours|
SRVR_COMFR1 | |ngimrcprod1|D:\sba81\siebsrvr| |Echec de la poignÃ©e de main|

Grep-ing of the Siebel log files have shown very long execution time for the Comm Session Manager BS. Excerpt from the log below (full file in attachment)

0

Howdy, Stranger!

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

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

Category Leaderboard

Top contributors this month