https://bz.apache.org/bugzilla/show_bug.cgi?id=58970
reda.housniala...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
--- Comment #5 from reda.housniala...@gmail.com ---
I am sorry, I wasn't clear enough.
Slash and me are working in the same company, so I can assure you that the
uploaded thread dump is about this issue.
We have a lot of trafic on AJP and less on http NIO because all non websocket
traffic is going through httpd modjk and then AJP connector.
Since modjk can't deal with websocket connections, http NIO connector is here
to only manage websocket traffic.
Here is what we do to systematically reproduce the issue:
- From a nodejs application we try to establish 20 000 atmosphere connections
using websocket transport to the app running in tomcat 8.0.30
- Once we hit the max connection, we wait about 1 minute
- Then we kill violently the node application and relaunch it to establish 20
000 new atmosphere connections
- If the http connector is still alive, we repeat the whole operation
It takes about 3 attemps to crash the http connector.
In the end, the node app is totally stopped, there is no more connection to the
tomcat http nio connector and yet the connector is totally frozen.
>From what I have seen, comparing healty tomcat tdump and tomcat with frozen
connector tdump, I can see that when connector is frozen, all http nio
acceptors thread are in PARKING status.
--
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
