Siebel Inbound Web Services integration scenario that uses anonymous session pool may not recover after temporary outage of the EAI Object Manager Component
(Doc ID 852611.1)
Last updated on DECEMBER 15, 2024
Applies to:
Siebel CRM - Version 8.0 [20405] to 8.1.1.2[21215] [Release V8]Information in this document applies to any platform.
Symptoms
Anonymous User Session Pool of the Siebel Inbound Web Services intgeration approach may not recover after Siebel EAI OM Server Component restart.
The scenario of typical occurrence is following:
(1) An external Application performs Siebel Inbound Web Service call using the approach which is using the Anonymous Session Pool. For example it could be a WS-Security headers usage in SOAP call to the "/eai_anon_enu" URL or a solution outlined in the <Note 601681.1> " How to create a totally anonymous web service in Siebel?" document..
(2) The call is successfully executed by the Siebel EAI Object Manager (OM) Component task and the Anonymous Session pool is filled by one running session, ready to accept next calls coming.
(3) The Siebel EAI OM Component gets temporary unavailable (Siebel Component restarted or the entire Siebel Server restart), while the Siebel Web Server (that hosts the Siebel Web Server Extension - SWSE module) continues to run and keep the Anonymous Session pool untouched.
Typical detailed traces in the SWSE log file could look like below, when the SWSE detects outage of the EAI OM (shutdown command):
(Note: The EAI OM Siebel session taken into Anonymous Session Pool is: !5.fc0)
SisnapiLayerLog Error 1 ... [SISNAPI] Async Thread: connection (0x24c88c0), error (1180671) while reading message
SisnTcpIp SisnSockDetail 4 ... [TCPIP-client] socket() closed descriptor = 724 from 0.0.0.0:3215 to 10.10.0.11:2381
SessMgr MsgReceive 5 ... [SESSMGR] CB: conn 0x23f2620, url siebel.TCPIP.None.None://.../EAIObjMgr_enu/!5.fc0, mbuf 0x0, mlen 0, err 1180671
SessMgr SessMgrGeneric 4 ... [SESSMGR] conn 0x23f2620: found error code (1180671), error info (NULL)
SessMgr MsgReceive 5 ... [SESSMGR] CB: conn 0x23f2620, url siebel.TCPIP.None.None://.../EAIObjMgr_enu/!5.fc0, mbuf 0x0, mlen 0, err 3670029
SessMgr SessMgrGeneric 4 ... [SESSMGR] conn 0x23f2620: found error code (3670029), error info (NULL)
SessMgr ConnClose 5 ... [SESSMGR] conn 0x23f2620: ctx 0x2e363d8, url 0x<?INT?> cleaned up
SisnapiLayerLog Trace 3 ... [SISNAPI]: releasing connection (0x24c88c0), refCount = 1
SisnapiLayerLog Trace 3 ... [SISNAPI]: releasing connection (0x24c88c0), refCount = 0
...."
(4) The external application performes the next SOAP call and this call fails with the component outage, because the the SWSE can not access the EAI OM sesison context using the information obtained frm the Anonymous Session pool.
The session added to the pool by SWSE module does not point anymore to the actual EAI OM session context, because the accordant component task has been stopped, at the EAI OM component outage.
Typical detailed traces in the SWSE log file outline the connection issue like below:
(Note: The EAI OM Siebel session taken for use from the Anonymous Session Pool is: !5.fc0 - same as in step before)
"...
ProcessPluginRequest ProcessPluginRequestDebug 5 ... [SWSE] Created EAI request handler.
ProcessPluginState ProcessPluginStateDebug 5 ... [SWSE] Switching to Start state.
ProcessPluginRequest ProcessPluginRequestDebug 5 ... [SWSE] User spec: REMOTE_USER
ProcessPluginRequest ProcessPluginRequestDebug 5 ... [SWSE] POST query string: SWEExtSource=SecureWebService&SWEExtCmd=Execute
ProcessPluginState ProcessPluginStateDebug 5 ... [SWSE] Switching to HTTP_REQ state.
ProcessPluginRequest ProcessPluginRequestDetail 4 ... [SWSE] Anon pool has 1 of 1 sessions available
ProcessPluginRequest ProcessPluginRequestDetail 4 ... [SWSE] Pulled an anon session: !5.fc0.90000a.4a37c661 taken from the pool.
ProcessPluginRequest ProcessPluginRequestDetail 4 ... [SWSE] Checked out anon session: !5.fc0.90000a.4a37c661.
ProcessPluginState ProcessPluginStateDebug 5 ... [SWSE] Switching to Session state.
SessMgr MsgSend 5 ... [SESSMGR] SendMsg:_SendMsgSync(siebel.TCPIP.None.None://.../EAIObjMgr_enu/!5.fc0.90000a.4a37c661, 0x30bf9a8)
SisnTcpIp SisnSockDetail 4 ... [TCPIP-client] socket() opened descriptor = 724 from ...
SessMgr ConnOpen 3 ... [SMCONN] opened connection to siebelURL (siebel.TCPIP.None.None://.../EAIObjMgr_enu/!5.fc0)
SessMgr ConnOpen 3 ... [SMCONN] SISNAPI connection opened in 0.001021 secs
...
SisnTcpIp SisnSockError 1 ... [TCPIP-client] recv() failed for sd=724 (err=10054 | An existing connection was forcibly closed by the remote host (peer).)
SessMgr ConnOpen 3 ... [SMCONN] Hello handshake to (siebel.TCPIP.None.None://.../EAIObjMgr_enu/!5.fc0) failed in 1 secs
GenericLog GenericError 1 ... (smconn.cpp (318) err=1180671 sys=0) SBL-NET-01023: Peer disconnected
...
GenericLog GenericError 1 ... (ssmsismgr.cpp (771) err=3670020 sys=0) SBL-SSM-00004: SISNAPI Hello failed. The server component could be down.
SessMgr MsgReceive 5 ... [SESSMGR] CB: conn 0x2e3edd0, url siebel.TCPIP.None.None://.../EAIObjMgr_enu/!5.fc0, mbuf 0x0, mlen 0, err 3670029
SessMgr SessMgrGeneric 4 ... [SESSMGR] conn 0x2e3edd0: found error code (3670029), error info (NULL)
SessMgr ConnClose 5 ... [SESSMGR] conn 0x2e3edd0: ctx 0x2e45618, url 0x<?INT?> cleaned up
SisnapiLayerLog Trace 3 ... [SISNAPI]: releasing connection (0x24c88c0), refCount = 0
GenericLog GenericError 1 ... (ssmsismgr.cpp (1708) err=3670022 sys=0) SBL-SSM-00006: Error while sending message to server.
ObjMgrSessionLog Error 1 ... CSSUModel::InvokeSrvcMethod - Failed with Error=10879179 for service=Web Engine Interface, method=Request
ProcessPluginRequest ProcessPluginRequestError 1 ... [SWSE] Error invoking service method 10879179
ProcessPluginRequest ProcessPluginRequestError 1 ... [SWSE] Error Message 0 : error 10879179 : Not connected to the server.
SBL-SSM-00006: Error while sending message to server.
ProcessPluginRequest ProcessPluginRequestDetail 4 ... [SWSE] InvokeSrvcMethod Timing: 0.60115 seconds
ProcessPluginState ProcessPluginStateError 1 ... [SWSE] Invoke service method failed.
ProcessPluginState ProcessPluginStateDetail 4 ... [SWSE] Closing Session : siebel.TCPIP.None.None://.../EAIObjMgr_enu/!5.fc0.90000a.4a37c661 ....
SessMgr MsgSend 5 ... [SESSMGR] SendMsg:_SendMsgSync(siebel.TCPIP.None.None://.../EAIObjMgr_enu/!5.fc0.90000a.4a37c661, 0x30bf9f8)
...
siebel.TCPIP.None.None://.../EAIObjMgr_enu/!5.fc0, mbuf 0x0, mlen 0, err 3670029
SessMgr SessMgrGeneric 4 ... [SESSMGR] conn 0x2e3edd0: found error code (3670029), error info (NULL)
SessMgr ConnClose 5 ... [SESSMGR] conn 0x2e3edd0: ctx 0x2e4ed18, url 0x<?INT?> cleaned up
SisnapiLayerLog Trace 3 ... [SISNAPI]: releasing connection (0x24c88c0), refCount = 0
SessMgr ConnClose 5 ... [SESSMGR] Close(siebel.TCPIP.None.None://.../EAIObjMgr_enu/!5.fc0.90000a.4a37c661) failed - rc = 3670020
ProcessPluginState ProcessPluginStateDetail 4 ... [SWSE] Closing Session : siebel.TCPIP.None.None://.../EAIObjMgr_enu/!5.fc0.90000a.4a37c661 Lifespan : 0.0000
ProcessPluginState ProcessPluginStateDetail 4 ... [SWSE] CloseSession Timing: 0.00000 seconds
ProcessPluginRequest ProcessPluginRequestError 1 ... [SWSE] Set Error Response (Session: Error: 10879179 Message: Not connected to the server.
SBL-SSM-00006: Error while sending message to server.)
..."
(5) The external application receives the HTTP 500 error and retries the SOAP Call again.
This time the could could go, if the Anonymous connection pool contained no other sessions.
Otherwise (which is possible during the massive SOAP calls cases) the error remains persistent.
Typical detailed traces in the SWSE log file outline the connection issue like below:
ProcessPluginRequest ProcessPluginRequestDetail 4 ... [SWSE] Anon pool has 0 of 10 sessions available
ProcessPluginRequest ProcessPluginRequestError 1 ... [SWSE] Could not get an anon session...PROBLEM
ProcessPluginRequest ProcessPluginRequestError 1 ... [SWSE] Failed to obtain a session ID. No anonymous user available for processing requests. This server is too busy to process any new connection requests at the moment.
ProcessPluginRequest ProcessPluginRequestError 1 ... [SWSE] Set Error Response (Session: Error: 10944627 Message: No anonymous user available for processing requests. This server is too busy to process any new connection requests at the moment.)
..."
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 |
| Cause |
| Solution |
| References |