Unable to auto-start driver when using certificate for SSL encryption

  • 3007829
  • 17-Aug-2006
  • 26-Apr-2012

Environment

Novell NetWare 6.5 Support Pack 5
Novell eDirectory 8.7.3.7 for NetWare 6.5
Novell DirXML Identity Manager 3.0

Situation

When using a certificate for SSL encryption between two eDirectory drivers, the driver would not start automatically (after restarting eDirectory). The following error was present in the trace:
[06/15/06 10:58:19.791]: edir trace PT: : Creating JSAS SecureServerSocket
[06/15/06 10:58:19.793]: edir trace PT:
DirXML Log Event -------------------
Driver: \NOS-TEST-TREE\NOS\Services\NOS_Driver_Set\NOS to IDV
Channel: Publisher
Status: Error
Message: Code(-9010) An exception occurred: java.lang.NoClassDefFoundError: com/novell/service/security/net/SecureServerSocket
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at com.novell.service.security.net.nssl.SecureServerSocketFactory.create(SecureServerSocketFactory.java:152)
at com.novell.nds.dirxml.driver.ssl.nssl.NSSLKmoFactory.createServerSocket(NSSLKmoFactory.java:86)
at com.novell.nds.dirxml.driver.nds.PublicationShimImpl.initListener(PublicationShimImpl.java:256)
at com.novell.nds.dirxml.driver.nds.PublicationShimImpl.start(PublicationShimImpl.java:301)
at com.novell.nds.dirxml.engine.Publisher.run(Publisher.java:315)
at java.lang.Thread.run(Thread.java:534)

Resolution

Comparison of a working system's CONFIG.TXT file against the non-working system's CONFIG.TXT file showed some modules being loaded in the AUTOEXEC.NCF and STARTUP.NCF in a different order. The following was done to resolve the issue:
  1. Disabled Hyper-Threading
  2. Replaced ACPIDRV.PSM in Startup.NCF with MPS14.PSM
  3. Removed ACPISBD.NLM from Autoexec.NCF.