"Caching ObjectType" Cause Inbound Web Services to Time Out
(Doc ID 2576228.1)
Last updated on AUGUST 26, 2019
Applies to:Siebel CRM - Version 19.1 and later
Information in this document applies to any platform.
On : 19.1 version, Siebel EAI
When an inbound web service call is made right after an EAI PID starts up, logs show thousands of "caching objecttype" calls loading repository objects into memory cache, causing a delay of 2 minutes or more.
Client applications are timing out when this happens.
Cache should be loaded at PID startup, before any web service call reaches the EAI component.
That way, when even the very first request reaches EAI, the repository is already in memory and there is no delay.
The issue can be reproduced at will with the following steps:
1. For simplicity, set Min MT = Max MT = 1 .
2. Stop the siebel server.
3. Start it back up with NO USERS.
4. Use SOAPUI to send a request to any web service. Notice it takes more than 2 minutes to respond.
5. Send a second request and confirm from the second request on
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