Traveler 8.5.0.1 crash

We have noticed on a few occations that our Traveler server crashes. The following shows the log.nsf lines from just before the crash.Version of Traveler is: Lotus Notes Traveler 8.5.0.1 Build 200902181237

Version of Domino is: Lotus Domino server Release 8.5 HF84|February 18, 2009

First time noticed was after implementing traveler policy (explisit policy for 2 users only) but I don’t know what influence this might have had.

Have you experienced something similar?

Thanks

Ove

27.05.2009 21:13:24 HTTP JVM: java.net.SocketException: Connection reset

27.05.2009 21:13:24 HTTP JVM: at java.net.SocketInputStream.read(SocketInputStream.java:181)

27.05.2009 21:13:24 HTTP JVM: at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2279)

27.05.2009 21:13:24 HTTP JVM: at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2292)

27.05.2009 21:13:24 HTTP JVM: at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2763)

27.05.2009 21:13:24 HTTP JVM: at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:793)

27.05.2009 21:13:24 HTTP JVM: at java.io.ObjectInputStream.(ObjectInputStream.java:293)

27.05.2009 21:13:24 HTTP JVM: at com.lotus.sync.servlet.ConnectionListener$CLWorker.run(ConnectionListener.java:1010)

27.05.2009 21:13:26 Chronos: Full text indexer terminating

27.05.2009 21:13:28 HTTP JVM: Traveler: Lotus Traveler task is not operational. Client request denied for CN=User Name/OU=Department/O=Organization.

27.05.2009 21:14:22 Process C:\Lotus\Domino\ntraveler.EXE (2708/0xA94) has terminated abnormally

Subject: Traveler crash

The logs below show that the server has crashed, but do not show the actual crash itself. For better diagnostics the next time this happens I would run nsd on a command prompt in the Domino Programs directory then zip and submit the IBM_TECHNICAL_SUPPORT directory as well as the traveler\log directory to IBM Support.

Also might be worth upgrading to the latest maintenance level for the traveler Server to see if problem still exists.

See latest recommended maint here:

http://www-01.ibm.com/support/docview.wss?uid=swg24019529