Out Of Memory Crashes Due To PrepareQueryCache Where XPath.LRUSize And XPath.flushTimeout Not Set
Last updated on NOVEMBER 01, 2017
Applies to:Oracle Utilities Mobile Workforce Management - Version 2.0 and later
Oracle Real-Time Scheduler - Version 2.1.0 and later
Oracle Utilities Framework - Version 4.1.0 and later
Information in this document applies to any platform.
Approximately 2 times a month, depending on the user requests, the system crashes in an out of memory situation.
The heapdump captured on outofmemory shows this class consuming most memory: com.splwg.mwm.support.scheduler.process.SchedulerLifecycleManager
This is occurring on an IBM JDK, and IBM support has suggested that 'com/splwg/base/support/scripting/PreparedXQueryCache' is leaking/consuming >50% memory.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms