My Oracle Support Banner

InfoManager Instance Stalls With java.lang.IllegalMonitorStateException In Instance Log (Doc ID 2027031.1)

Last updated on AUGUST 27, 2020

Applies to:

Oracle Knowledge - Version 8.4.6 and later
Information in this document applies to any platform.

Symptoms

InfoManager instance becomes unresponsive. Within the instance log java.lang.IllegalMonitorStateException exceptions are present. Examination of thread dumps reveals many threads in the following state:

java.lang.Thread.State: WAITING
at sun.misc.Unsafe.park(Native Method)
- waiting to lock <64d7a649> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) owned by "http-8226-8" t@145

with the owning thread in a state such as:

java.lang.Thread.State: WAITING
at java.lang.Object.wait(Native Method)
- waiting on <1045d588> (a com.webobjects.appserver.WOSessionStore$TimeoutEntry)
at java.lang.Object.wait(Object.java:485)
at com.webobjects.appserver.WOSessionStore.checkOutSessionWithID(WOSessionStore.java:191)
at com.webobjects.appserver.WOApplication.restoreSessionWithID(WOApplication.java:1924)
at er.extensions.appserver.ERXApplication.restoreSessionWithID(ERXApplication.java:2028)
at com.webobjects.appserver._private.WOComponentRequestHandler._dispatchWithPreparedApplication(WOComponentRequestHandler.java:324)
at com.webobjects.appserver._private.WOComponentRequestHandler._handleRequest(WOComponentRequestHandler.java:369)
at com.webobjects.appserver._private.WOComponentRequestHandler.handleRequest(WOComponentRequestHandler.java:445)
at com.webobjects.appserver.WOApplication.dispatchRequest(WOApplication.java:1698)

etc.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.