[OPENDJ-2199] Error at end of GUI setup: LDAP response read timed out Created: 03/Jul/15  Updated: 08/Nov/19  Resolved: 07/Mar/17

Status: Done
Project: OpenDJ
Component/s: None
Affects Version/s: 3.0.0, 2.8.0
Fix Version/s: Not applicable

Type: Bug Priority: Minor
Reporter: Sebastien Bertholet [X] (Inactive) Assignee: Matthew Swift
Resolution: Won't Fix Votes: 0
Labels: None
Environment:

Ubuntu 14.04 / java 1.8.0_25


Attachments: Text File opendj-setup-8821181083867847187.log    
Dev Assignee: Matthew Swift

 Description   

Using DJ2.8 RC5 to do a GUI setup of a first DJ instance with replication enabled: everything looks ok (import of 10k entries succeeds) until last step where we get:

An unexpected error occurred configuring server lab03-fr.internal.forgerock.com:5389. The error is: org.opends.server.admin.client.CommunicationException: A communication problem occurred while contacting the server: LDAP response read timed out, timeout used:-1ms.
 Hide Details
           An unexpected error occurred configuring server lab03-fr.internal.forgerock.com:5389. The error is: org.opends.server.admin.client.CommunicationException: A communication problem occurred while contacting the server: LDAP response read timed out, timeout used:-1ms.
           org.opends.quicksetup.installer.InstallerHelper.configureReplication(InstallerHelper.java:648)
           org.opends.quicksetup.installer.Installer.configureReplication(Installer.java:1753)
           org.opends.quicksetup.installer.offline.OfflineInstaller.run(OfflineInstaller.java:187)
           java.lang.Thread.run(Thread.java:745)
 Root Cause:
           org.opends.server.admin.client.CommunicationException: A communication problem occurred while contacting the server: LDAP response read timed out, timeout used:-1ms.
           org.opends.server.admin.client.ldap.LDAPDriver.adaptNamingException(LDAPDriver.java:505)
           org.opends.server.admin.client.ldap.LDAPManagedObject.addNewManagedObject(LDAPManagedObject.java:270)
           org.opends.server.admin.client.spi.AbstractManagedObject.commit(AbstractManagedObject.java:340)
           org.opends.server.admin.std.meta.ReplicationDomainCfgDefn$ReplicationDomainCfgClientImpl.commit(ReplicationDomainCfgDefn.java:1358)
           org.opends.quicksetup.installer.InstallerHelper.configureReplication(InstallerHelper.java:635)
           org.opends.quicksetup.installer.Installer.configureReplication(Installer.java:1753)
           org.opends.quicksetup.installer.offline.OfflineInstaller.run(OfflineInstaller.java:187)
           java.lang.Thread.run(Thread.java:745)
 Root Cause:
           javax.naming.NamingException: LDAP response read timed out, timeout used:-1ms.; remaining name 'cn=dc\=example\,dc\=com,cn=domains,cn=Multimaster Synchronization,cn=Synchronization Providers,cn=config'
           com.sun.jndi.ldap.Connection.readReply(Connection.java:478)
           com.sun.jndi.ldap.LdapClient.processReply(LdapClient.java:889)
           com.sun.jndi.ldap.LdapClient.add(LdapClient.java:1041)
           com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:808)
           com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:341)
           com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:268)
           javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:202)
           org.opends.server.admin.client.ldap.JNDIDirContextAdaptor.createEntry(JNDIDirContextAdaptor.java:183)
           org.opends.server.admin.client.ldap.LDAPManagedObject.addNewManagedObject(LDAPManagedObject.java:256)
           org.opends.server.admin.client.spi.AbstractManagedObject.commit(AbstractManagedObject.java:340)
           org.opends.server.admin.std.meta.ReplicationDomainCfgDefn$ReplicationDomainCfgClientImpl.commit(ReplicationDomainCfgDefn.java:1358)
           org.opends.quicksetup.installer.InstallerHelper.configureReplication(InstallerHelper.java:635)
           org.opends.quicksetup.installer.Installer.configureReplication(Installer.java:1753)
           org.opends.quicksetup.installer.offline.OfflineInstaller.run(OfflineInstaller.java:187)
           java.lang.Thread.run(Thread.java:745)
 
 If you want to report this error, provide the contents of file /tmp/opendj-setup-8821181083867847187.log

It looks like we get an ldap timeout while configuring replication.
However, if we restart the server after the setup, it seems to work without any problem and we can even successfully replicate it to another DJ instance.



 Comments   
Comment by Ludovic Poitou [ 07/Mar/17 ]

This issue will not be fixed as the setup tool has been rewritten with DJ 4.0 and it no longer has a GUI.

Comment by Matthew Swift [ 07/Nov/19 ]

Moved to closed state because the fixVersion has already been released.

Generated at Wed Oct 21 11:02:31 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.