Refreshing the Meta Data Cache Fails With a Timeout Exception
(Doc ID 1345558.1)
Last updated on SEPTEMBER 10, 2019
Applies to:
Oracle Communications Order and Service Management - Version 6.3.1 and laterInformation in this document applies to any platform.
Symptoms
Refreshing the meta data cache fails with a timeout exceptionWhen (un)registering plugins aginst OSM cartridges, the refresh meta data cache at the end of each registration action failed with a transaction timeout. This was due to the fact that it needs more time than the amount given with the weblogic transation timeout limit (600 sec).
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 |