Slow Gateway Response Leads to Failures in SD_isPIDExistsInRegistry_internal , Exception code 0xe06d736308 and HTTP-500 Responses to Inbound SOAP Web Services
(Doc ID 2902974.1)
Last updated on OCTOBER 15, 2022
Applies to:
Siebel CRM - Version 22.1 and laterInformation in this document applies to any platform.
Symptoms
On a Production Siebel environment, some of the Inbound anonymous calls are failing intermittently:
Localhost access log:
POST /siebel/app/eai_anon/enu/?SWEExtSource=SecureWebService&SWEExtCmd=Execute HTTP/1.1 500
Enterprise log:
ServerLog ProcessExit 1 0000000463003d74:0 2022-08-22 10:42:55 EAIObjMgr_enu 14868 0xe06d736308 Process 14868 exited with error - Exception code 0xe06d736308
EAIObjMgr log:
NameServerLayerLog Error 1 000006fe63003a14:0 2022-08-22 10:42:55 Gateway Registry exists failed: Registry generic exception.
GenericLog GenericError 1 000006fe63003a14:0 2022-08-22 10:42:55 SD_isPIDExistsInRegistry_internal: Error occurred while checking registry.
The issue happens regularly in production and is not specific to any one web service.
To observe it :
1. Trigger the external inbound requests
2. Monitor the AI logs
3. See some of those calls failing and others completing just fine.
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 |