tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 55241] New: maxConnections for BIO connector leads to acceptor stop
Date Thu, 11 Jul 2013 13:10:13 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=55241

            Bug ID: 55241
           Summary: maxConnections for BIO connector leads to acceptor
                    stop
           Product: Tomcat 7
           Version: 7.0.34
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Connectors
          Assignee: dev@tomcat.apache.org
          Reporter: kudryashov@gmail.com

It looks like issue #53173 is not fixed completely. Recently we had a similar
issue under Tomcat 7.0.34 / BIO connector when Acceptor thread hung forever on
LimitLatch:

"http-bio-63.215.91.155-8443-Acceptor-0" daemon prio=10 tid=0x0000000001656800
nid=0x540c waiting on condition [0x00007fb64aa2f000]
   java.lang.Thread.State: WAITING (parking)
    at sun.misc.Unsafe.park(Native Method)
    - parking to wait for  <0x0000000763e49970> (a
org.apache.tomcat.util.threads.LimitLatch$Sync)
    at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
    at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
    at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
    at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
    at
org.apache.tomcat.util.threads.LimitLatch.countUpOrAwait(LimitLatch.java:115)
    at
org.apache.tomcat.util.net.AbstractEndpoint.countUpOrAwaitConnection(AbstractEndpoint.java:718)
    at
org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:210)
    at java.lang.Thread.run(Thread.java:722)

Tomcat is run with maxThreads="1000" and maxConnections="1000"
This can be reproduced via the following scenario in our environment:
1. Start tcpkill in the following way to kill the connection from client to
Tomcat for requests larger than 2000:
tcpkill host <host> and port 8185 and greater 2000
2. Access Tomcat several times. As soon as the number of ClientAbortException
errors reaches the number of threads (or connections), Acceptor thread blocks
in WAITING state and Tomcat stops accepting new connections

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message