On 06/08/2013 03:45, Bob DeRemer wrote: > QUESTION > > Is anyone aware of any problems using the apr/native connector + > websockets in Tomcat 7.0.42?
I'm not aware of any reports. > BACKGROUND > > We are trying to see how many concurrent websocket connections Tomcat > will handle running on Windows Server. We wrote a multi-threaded java > console app that spins up a thread-per simulated websocket client. In > each thread, we are using a separate Ning websocket client. > Unfortunately, we can’t connect more than a few connections before we > start getting websocket errors. What sort of errors? > If we change the connector to use NIO, the sporadic connection errors > seem to go away, but then we find that after about 200 connections, the > communication seems to hang. This happens if all connections are made > from a single test client instance or spread across multiple client > instances. That suggests at least some issue with APR/native and WebSocket. > We’re trying to determine where the problem lies and if it’s in our use > of Ning in a multi-threaded client app, Tomcat connector configuration, > use of Tomcat websockets on Windows or something else. The focus in Tomcat 7 is going to move to the JSR356 implementation pretty soon. I'd suggest looking at that rather than putting effort into Tomcat 7's current implementation. > If anyone has any suggestions, I would greatly appreciate it. If you > need additional information, please don’t hesitate to ask. I'll look into adding a concurrent client test to the Tomcat unit tests. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
