Identity Synchronization for Windows: Connector Became Unresponsive And Caused Synchronization Failure With Error From Message Queue: java.lang.OutOfMemoryError: Java heap space (Doc ID 1300289.1)

Last updated on SEPTEMBER 16, 2016

Applies to:

Oracle Directory Server Enterprise Edition - Version 6.0 and later
Information in this document applies to any platform.
NOTE: Please ensure the correct version of MQ is being used for the version of iSW being used by checking the installation instructions here:

- For iSW 6.0, MQ version 3.6 is required:
http://download.oracle.com/docs/cd/E19424-01/821-0422/isw-install/index.html

- For iSW 6.0 SP1, minimum requirement is version 3.7 U1, optimum version is 4.3:
http://download.oracle.com/docs/cd/E19656-01/821-1581/index.html


Symptoms

A Connector, such as the AD connector becomes non-responsive and causes Synchronization failure.

Errors are seen in the Message Queue logs as per the following example:

[08/2/2011:09:09:05 JST] Error T:PSW_AuditLoggingTopic:failed to parse
message(size=1149) from vrecord(VRecordRAF: start=13848;
cap=1792;state=2;index=16):
java.lang.OutOfMemoryError: Java heap space
[08/2/2011:09:11:23 JST] Error T:PSW_AuditLoggingTopic:failed to parse
message from vrecord(VRecordRAF: start=13848; cap=1792;state=2;index=16):
java.io.IOException: java.lang.OutOfMemoryError: Java heap space
[08/2/2011:09:12:06 JST] Error [B4107]: Message from store
Can not read 1078323-150.65.1.4(cf:df:a3:71:7:d4)-32848-1297122741651:
java.io.IOException: java.lang.OutOfMemoryError: Java heap space

[08/2/2011:10:22:49 JST] [B1066]: [B0060]: Close because the Service is shutting down <---- MQ is stopping.
: CNN100@150.65.1.4:32871->ssljms:32824 Count=2
[08/2/2011:10:22:49 JST] Timer shutting down :
java.lang.IllegalStateException: Timer already cancelled.
[08/2/2011:10:22:49 JST] Timer shutting down :
java.lang.IllegalStateException: Timer already cancelled.
[08/2/2011:10:22:49 JST] [B1007]: Stop the jms service at Protocol tcp(host = *, port=0,
mode=dedicated)
[08/2/2011:10:22:49 JST] [B1077]: broadcasting the good-bye to all connections...
[08/2/2011:10:22:49 JST] [B1078]: flashing the good-bye message...
[08/2/2011:10:22:49 JST] [B1063]: Complete
[08/2/2011:10:22:55 JST] [B1048]: broker was stop completely.
[08/2/2011:10:22:59 JST]

Also the following error from the iSW /logs/central/audit log:

"Failed to establish a connection to the Sun Java(TM) System Message
Queue Broker because of a JMSException:
com.sun.messaging.jms.JMSException

Cause

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