The 'stderr.log' messages are normal (assuming that you've set an soTimeout, which I wouldn't recommend). I'd need to see more context for the jk2.log messages (unless they are caused by a really short timeout from above).
<[EMAIL PROTECTED]> wrote in message 01BB14133B43D2118ED300104B9C202B03CFC314@SQ_EXG1">news:01BB14133B43D2118ED300104B9C202B03CFC314@SQ_EXG1... > I am hoping that someone sees these errors below and can immediatly tell me > that they are expected and/or normal. I am seeing hundreds of the same error > in the stderr.log. Anyone see these before....either of them? > > Best, > > Stephen > > > > > jk2.log > ----------------------- > [Mon Feb 10 19:04:00 2003] (error) [jk_channel_socket.c (557)]: > channelSocket.receive(): Error receiving message body -1 104 > [Mon Feb 10 19:04:00 2003] (error) [jk_workerEnv.c (482)]: > workerEnv.processCallbacks() Error reading reply > [Mon Feb 10 19:04:00 2003] (error) [jk_worker_ajp13.c (407)]: > ajp13.service() ajpGetReply recoverable error 21000 > > stderr.log > ----------------------- > Feb 10, 2003 7:37:05 AM org.apache.jk.common.ChannelSocket processConnection > INFO: connection timeout reached > Feb 10, 2003 7:37:18 AM org.apache.jk.common.ChannelSocket processConnection > INFO: connection timeout reached > Feb 10, 2003 7:38:03 AM org.apache.jk.common.ChannelSocket processConnection > INFO: connection timeout reached > Feb 10, 2003 7:38:21 AM org.apache.jk.common.ChannelSocket processConnection > INFO: connection timeout reached > Feb 10, 2003 7:38:44 AM org.apache.jk.common.ChannelSocket processConnection > INFO: connection timeout reached > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]