My Oracle Support Banner

Siebel AOM Crashes If The CTI Session Is Disconnected While NotReady Popup Is Open (Doc ID 2016884.1)

Last updated on NOVEMBER 22, 2019

Applies to:

Siebel CTI - Version 8.1.1.11.9 [IP2013] and later
Information in this document applies to any platform.

Symptoms

In Siebel version 8.1.1.11.9

Siebel OM crashes if the CTI session is disconnected while NotReady popup is opened

Problem Description
---------------------------------------------------
We are getting Siebel OM crashes by following these steps:

1. Login to Siebel with a CTI enabled user
2. Login to CTI
3. Open the NotReady selection popup by pressing the NotReady button on the CTI toolbar
4. Create a disconnection scenario between the CTI Toolbar and the Siebel server (can be done by disabling the network temporarily or by letting the workstation enter sleep/standby mode)
5. Make sure you get something like:


NFO:About to invoke ShellUIExit because it has been 120 seconds since the last successful push message sent to browser. This exceeds the ChannelCleanupTimer value 60 seconds. Browser is most likely frozen. AccumulatedTime=0, CmdTime=0
INFO:ResetAgentActiveInfo ok
INFO:User XXXXXX_XX, key xxxxxxxxxxxxxx exited.

6. After the log message above press OK to select a NotReady Reason.
7. Siebel will crash

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.