https://issues.apache.org/bugzilla/show_bug.cgi?id=54105
Konstantin Kolinko <knst.koli...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Konstantin Kolinko <knst.koli...@gmail.com> ---
1. There is nothing wrong with Acceptor thread waiting for incoming
connections.
It is its job to wait for those.
2. "2" is the value of JkHandler.ERROR.
Nothing more can be said from that.
3. The Catalina$CatalinaShutdownHook thread ("Thread-19") is stalled in
unLockSocket(). That is, trying to open a new connection to Tomcat. That is
normal.
If the acceptor thread is in good state (waiting on a socket) and new
connections cannot be made, the cause is somewhere in the network libraries,
out of the control of Tomcat.
If you need further help with it, ask on the users list.
Maybe you could use other tools to diagnose your network, maybe you are hitting
ulimits.
Maybe you have hit OutOfMemory some time earlier (and as a consequence your JVM
is hardly usable any more).
4. A "critical" issue?
Note that 6.0.29 is more than 2 years old. A number of issues has been fixed
since then, including some issues with AJP protocol and some security issues.
Closing as INVALID.
BTW, the org.apache.jk implementation of AJP protocol was removed from later
versions of Apache Tomcat. Whatever this issue is, those classes do not exist
in Tomcat 7 and later.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
