Hi everyone,

whenever I stop/restart ndsd (or the OS) on my SLES9/IDM35 machine, the remoteloader instances running as a windows service that start native mode drivers (AD and a custom one, based on the skeleton driver) will fail. This does not happen with RLs instances running java-based drivers like the Notes, LDAP, DelText and JDBC.

Windows event log has this:

Driver : \MUMMERT-META\de\mummert\hamburg\DIRXML_DRVSET01\DRV_DOM-ADMIN
Thread : Subscriber Channel
Object :
Message : Connection was broken

Driver : \MUMMERT-META\de\mummert\hamburg\DIRXML_DRVSET01\DRV_DOM-ADMIN
Thread : Subscriber Channel
Object :
Message : SSL protocol failure: error:140D00CF:SSL routines:SSL_writerotocol is shutdown

and the RL trace looks like this:

DirXML: [09/26/07 11:42:34.02]:
DirXML Log Event -------------------
Driver = \MUMMERT-META\de\mummert\hamburg\DIRXML_DRVSET01\DRV_DOM-ADMIN
Thread = Connection Receiver
Level = warning
Message = SSL protocol-violating EOF found or I/O error:
DirXML: [09/26/07 11:42:34.02]:
DirXML Log Event -------------------
Driver = \MUMMERT-META\de\mummert\hamburg\DIRXML_DRVSET01\DRV_DOM-ADMIN
Thread = Subscriber Channel
Level = error
Message = Connection was broken
DirXML: [09/26/07 11:42:34.02]:
DirXML Log Event -------------------
Driver = \MUMMERT-META\de\mummert\hamburg\DIRXML_DRVSET01\DRV_DOM-ADMIN
Thread = Subscriber Channel
Level = fatal
Message = Connection was broken
DirXML: [09/26/07 11:42:34.05]:
DirXML Log Event -------------------
Driver = \MUMMERT-META\de\mummert\hamburg\DIRXML_DRVSET01\DRV_DOM-ADMIN
Thread = Subscriber Channel
Level = error
Message = SSL protocol failure: error:140D00CF:SSL routines:SSL_writerotocol is shutdown
DirXML: [09/26/07 11:42:34.05]: Loader: Stopping driver
DirXML: [09/26/07 11:42:34.05]: ADDriver: Driver::destroy
DirXML: [09/26/07 11:42:34.05]: ADDriver: driver destroy without publisher start
DirXML: [09/26/07 11:42:34.05]: ADDriver: Driver::~Driver()
DirXML: [09/26/07 11:42:34.08]: Loader: Waiting for DirXML to connect on 'TCP server socket, port 8090, address localhost, using SSL'...


But contrary to the last statement in the trace, the driver is not waiting for a connect but stopped and needs to be restarted. After that the log continues like this and the driver starts again:

DirXML: [09/26/07 12:30:33.35]: Loader: Verifying command port...
DirXML: [09/26/07 12:30:34.41]: Loader: Verifying driver can be loaded...
DirXML: [09/26/07 12:30:34.60]: ADDriver: Driver::destroy
DirXML: [09/26/07 12:30:34.60]: ADDriver: Driver::~Driver()
DirXML: [09/26/07 12:30:34.61]: Loader: Initializing SSL encryption...
DirXML: [09/26/07 12:30:45.80]: Loader: Waiting for DirXML to connect on 'TCP server socket, port 8090, address localhost, using SSL'...
DirXML: [09/26/07 12:30:56.24]: Loader: OpenSSL socket: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1
DirXML: [09/26/07 12:30:56.24]: Loader: Authenticating with DirXML...
DirXML: [09/26/07 12:30:56.30]: Loader: Received 'handshake' document
DirXML: [09/26/07 12:30:56.30]: Loader: XML Document:
DirXML: [09/26/07 12:30:56.30]: <handshake version="1.0">
<password><!-- content suppressed --></password>
</handshake>

Anyone else seeing this? As I said before, this happens with the AD and custom driver, both come as DLLs, java-based drivers do just fine and reconnect without problems.

Cheers, Lothar
--