Help with: javax.naming.CommunicationException: connection closed. Root exception is

[RobTyler]

Hi,

I have a connector that performs a look up on an LDAP directory, The
performs a lookup an active directory for the equivelant entry based on a
$cn=cn join syntax.

The LDAP lookup connector is called: EDSLookup (Lookup:Enabled), the Active
directory lookup connector is called CMSLookup (Lookup:passive). I have
detailed logging enabled for both connectors.

The invocation of the CMSLookup connector is done inside the
LookupSuccessful hook of the EDSlookup connector. "CMSLookup.lookup(work);"

Here is the error message I get:

2006-03-20 16:50:59,075 INFO [AssemblyLine.Scan-1941722852] - [CMSLookup]
LDAPConnector: findEntry where: (cn=XXX) in base =
DC=base1,DC=base2,DC=base3
2006-03-20 16:50:59,075 ERROR [AssemblyLine.Scan-1941722852] - [EDSLookup]
while evaluating "EDSLookup.lookup_ok"
javax.naming.CommunicationException: connection closed. Root exception is
java.io.IOException: connection closed
at com.sun.jndi.ldap.LdapClient.ensureOpen(LdapClient.java(Compiled Code))
at com.sun.jndi.ldap.LdapClient.search(LdapClient.java(Compiled Code))
at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java(Compiled Code))
at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java(Compiled Code))
at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java(Compiled Code))
at
com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java(Compiled
Code))
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java(Compiled
Code))
at
javax.naming.directory.InitialDirContext.search(InitialDirContext.java(Inlined
Compiled Code))
at com.ibm.di.connector.LDAPConnector.findEntry(Unknown Source)
at com.ibm.di.server.AssemblyLineComponent.lookup(Unknown Source)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled
Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at
org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java(Compiled
Code))
at org.mozilla.javascript.ScriptRuntime.call(ScriptRuntime.java(Compiled
Code))
at org.mozilla.javascript.gen.c9.call(EDSLookup.lookup_ok:10)
at org.mozilla.javascript.gen.c9.exec(EDSLookup.lookup_ok)
at com.ibm.di.server.AttributeMapping$SingleAttributeMap.eval(Unknown
Source)
at com.ibm.di.server.AttributeMapping.eval(Unknown Source)
at com.ibm.di.server.AssemblyLineComponent.trigger(Unknown Source)
at com.ibm.di.server.AssemblyLineComponent.trigger(Unknown Source)
at com.ibm.di.server.AssemblyLineComponent.handleSuccess(Unknown Source)
at com.ibm.di.server.AssemblyLine.msExecuteNextConnector(Unknown Source)
at com.ibm.di.server.AssemblyLine.executeMainStep(Unknown Source)
at com.ibm.di.server.AssemblyLine.executeMainLoop(Unknown Source)
at com.ibm.di.server.AssemblyLine.executeMainLoop(Unknown Source)
at com.ibm.di.server.AssemblyLine.executeAL(Unknown Source)
at com.ibm.di.server.AssemblyLine.run(Unknown Source)

I have several issues.

1) The above error repeats until the Assembly line is restarted. My Auto
reconnect number of retry settings are set to 1 retry after 10 seconds. on
both the calling and the called connector.
2) The directories in question are always up, even though the error is
reporting connection closed. Is there a way to tell if there is an actual
issue here? And which connector is having a problem that is generating this
error? ( we are in Lookup successful hook for the EDSlookup connector, so I
assume it has to be in the CMS {called connector}, but there is no logging,
detailed or otherwise to corroborate this.)
3) I have skip.entry() included in the Default On Error Hook for both
connectors, why does the assembly line go into a death spiral on this error?

IDI Version 6.0 build ididev_041111b, Windows Server 2003,

Thanks,
Rob Tyler

[Eddie Hartman]

Hi Rob,

This message would indicate that the connection to
the LDAP was closed. I am assuming your call to
lookup() is causing the error, but you could wrap
this script in a try-catch block to see if this is so:

try {
CMSLookup.lookup(work);
} catch (exc) {
task.logmsg("Error calling CMSLookup.lookup()");
task.dumpEntry(error); // Dump the error Entry object
}

Where is your EDS LDAP running?

-Eddie