Unable to Re-Login to Siebel Application When One Application Object Manager (AOM) Component Is Paused (Doc ID 2812797.1)

Last updated on SEPTEMBER 16, 2022

Applies to:

Symptoms

 The session status is not getting updated after user logs out while component is paused . Due to this at re-login user session is sent to the same server with component paused even if multiple Siebel Servers are online.

To pause a server component on a Siebel Server:

1. Navigate to Administration - Server Management screen, then the Components view.

2. In the Components list, select the server component of interest.

3. Note: Make sure that you select the server component on the Siebel Server of interest.

4. Click Pause.

For more details please refer to the System administration guide.

The issue can be reproduced at will with the following steps:

1. Setup an environment with multiple Siebel servers.

2. Login in the Call Center application.

3. Set the concerned component to pause in one Siebel server.

4. Log out from Call Center application.

5. Re-login to the Call Center application.

6. Following error is thrown in the browser: 

"You already have a Siebel session with unsaved data running in another

browser window. To save data from a second session go to the already open

session and either save and exit or continue to use that data.

You do not have unsaved data in your other session and wish to close it and

launch a new session. Click here"

7. When " Click here " is pressed a blank page is loaded showing message "Closed"

Pausing the component should prevent new log-ins to it, and requests should be routed to another Application Object Manager that is Online.

Due to this issue, users cannot re-login properly in the Call Center application while the component of one Siebel Server ( of many) is paused, and requests are still being sent to the paused one.

Cause

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