LDAP and CSSDK

MikeOlson

I have an application that communicates with both LDAP and Team Site.

I have had it running, but this morning I started moving some of the code around (general cleanup, no functional changes) and my code stopped working.

When I try and make an LDAP call I am getting a

javax.naming.CommunicationException: ldap-server:636 [Root exception is java.net.SocketException: java.lang.ClassNotFoundException: com.interwoven.cssdk.factory.DummySSLSocketFactory]
at com.sun.jndi.ldap.Connection.(Connection.java:197)
...

When I get this exception, I have not made any calls into the CSSDK,however I have imported some of the classes.

My guess is that something in some import is changing the default socket factory settings in my JVM.

Does anyone have any ideas what is doing this and how to make it stop?

Thanks
Mike

Bjorn

Does anyone have any ideas what is doing this and how to make it stop?

Not really, but my first suggestion would be to revert to the code that works, then do some type of diff to see what changed. If you're using an IDE like Eclipse, might you have mixed up some imports, so a class you think you're using isn't really the same class as was used prior to the cleanup? This is really easy to do if auto-imports are turned on in Eclipse and you're using classes that extend/implement the same or similar classes/interfaces.

The import directive just tells the compiler where to look if it can't find a given class in the java.lang package that is used within your class' methods or class definition. It's not like it runs anything when you use it or brings anything into the bytecode like it does in some other languages.

If you can't revert, then remove/comment-out what you believe is the offending code based on any stacktrace you have and go from there. Hopefully your class(es) is/are modular enough where they can withstand this kind of debugging without completely ripping them apart and causing more errors.