ISW Connector Goes Into "INSTALLED" State
Last updated on DECEMBER 18, 2012
Applies to:Oracle Directory Server Enterprise Edition - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
After a ISW restart. The idsync printstat showing the connectors are in SYNCHING state. The synchronization between the AD and the Sun DS is performing well.
But after administrator runs "idsync resync" command to sync a specific user's password, the ISW AD connector stops an goes to INSTALLED state. With this state, the idsync fails with the error "failed because one of the connector is not ready".
From the connector's error log, it has [26/Nov/2012:11:14:00.109 -0500] SEVERE 10 CNN101 xxxxx "Failed to establish a connection to the Sun Java(TM) System Message Queue Broker because of a JMSException: com.sun.messaging.jms.InvalidClientIDException: [C4052]: Client ID is already in use - CNN101"
The 'ps -ef | grep java' shows the double amount of java processes running for the ISW connector.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms