Engines logging off due to I/O exception

Engines logging off due to I/O exception

book

Article ID: KB0094302

calendar_today

Updated On:

Products Versions
TIBCO DataSynapse GridServer -
Not Applicable -

Description

Resolution:
If you are running a Gridserver manager on a Windows machine and encountering engine disconnects with a log similar to this:

04/08/09 18:39:56.031 WARNING: [JakartaHttpSupport$MethodRetryHandler] java.net.SocketException: Connection reset by peer: socket write error, will retry in 3000 msecs.
04/08/09 18:39:59.031 INFO: [org.apache.commons.httpclient.HttpMethodDirector] I/O exception caught when processing request: Connection reset by peer: socket write error
04/08/09 18:39:59.031 INFO: [org.apache.commons.httpclient.HttpMethodDirector] Retrying request
04/08/09 18:40:09.437 INFO: [EngineLoginPlugin] Initiating logoff

Removing the &ltGS_ROOT>\win32 directory will alleviate the situation. Remove the directory from all the managers. Since the file will be in use, stop the manager before attempting to delete.

The &ltGS_ROOT>\win32 directory contains the file resin.dll. It is used by Resin to enable native I/O. We have seen performance degradation when native I/O is used over java I/O. Turning off Resin native socket support by deleting the directory, will cause Java I/O to be used and thus improve performance on the grid.

Issue/Introduction

Engines logging off due to I/O exception