I'm trying to figure out what this means, and how to stop it... We're getting
following error repeated in our catalina.out logs:
Apr 24, 2009 8:42:24 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Apr 24, 2009 8:44:00 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Apr 24, 2009 8:46:36 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Apr 24, 2009 8:46:38 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Apr 24, 2009 8:46:39 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Apr 24, 2009 8:46:40 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Apr 24, 2009 9:44:17 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Apr 24, 2009 9:45:03 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Apr 24, 2009 10:10:42 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Apr 24, 2009 10:10:43 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Apr 24, 2009 10:10:45 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Apr 24, 2009 10:10:45 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Apr 24, 2009 10:16:05 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
...
It goes on like this all day long - every few minutes we get another error.
We'd like to know what's causing it - and whether there is any way to prevent
it (or even filter it if it isn't worth worrying about). Our production team is
a stickler for not logging things that don't require action (in production), so
they are really queasy about this repeated error.
FYI, our configuration is:
4 Apache 2.2.11 servers (running on Red Hat Linux boxes)
each Apache is currently running in a 1:1 AJP Proxy connection to 1 of:
4 tomcat 6.0.18 servers (running on Red Hat Linux boxes)
So "apache 1" connects only to "tomcat 1", and "apache 2" connects only to
"tomcat 2", etc.
(We're working on getting our tomcat clustering stable enough to deploy.)
One of the things that is preventing our roll out of full clustering is
understanding the nature of this error in the catalina.out logs.
Also, all 4 tomcat servers are identically configured with the same webapps,
and the apache servers are load-balanced, but setup with "sticky sessions" so a
browser will stay with the same apache once they connect.
We do have <distributable /> setup in our web.xml for one of our web apps, and
we have a clustering "basic" (the defaults from one of the docs on clustering)
setup in the 'server.xml' file. This seems to work - but we throw a lot of
errors when we actually try to use clustered sessions - so we're working
through those as quickly as we can.
--
Robin D. Wilson
Director of Web Development
KingsIsle Entertainment, Inc.
www.KingsIsle.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
