OIM Hangs And Fails To Restart Correctly In Cluster Configuration

(Doc ID 1308094.1)

Last updated on MARCH 30, 2017

Applies to:

Identity Manager - Version to
Identity Manager - Version to [Release 11g]
Identity Manager - Version and later
Information in this document applies to any platform.


With OIM configured in a cluster configuration there can be certain situations where OIM Application intermittently fails to restart on nodes in the cluster due to the initilization of JavaGroups hanging.  Note: In the case of OIM 9.x this can occur regardless of the application server used.

Thread dumps taken at start up will contain similar to the following:

java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x64851790> (a java.lang.Object)
at java.lang.Object.wait(Object.java:485)
at org.javagroups.JChannel.connect(JChannel.java:257)
- locked <0x64851790> (a java.lang.Object)
- locked <0x64851688> (a org.javagroups.JChannel)
at org.javagroups.blocks.NotificationBus.start(NotificationBus.java:116)
at com.opensymphony.oscache.plugins.clustersupport.JavaGroupsBroadcastingListener.initialize(JavaGroupsBroadcastingListener.java:96)


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