tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject Re: non blocking Websockets?
Date Sun, 03 Jun 2012 17:50:26 GMT
On 31/05/2012 18:45, Christian Finckler wrote:
> Am 31.05.2012 11:09, schrieb Mark Thomas:
>> On 31/05/2012 10:02, Christian Finckler wrote:
>>> Hello,
>>> as far I understood, the websocket implementation of tomcat is using one
>>> thread per client.
>>> Is there also a possibility to configure it to use non blocking IO?
>> No. That has not yet been implemented. It shouldn't be too hard provided
>> that non-blocking is used between messages and blocking is used during
>> messages. Obviously, the BIO connector will always use blocking.

Whoops. My bad. I implemented this already. NIO and APR/native will be
non-blocking between messages and have been since the first Tomcat
release to include WebSocket support. Note that all connectors will
block between the point the upgrade is started and the first message is

This was on my to-do list for a while and I simply forgot I had actually
implemented. Had I looked at the code first (like I just did) it would
have been clear that this was implemented.

Sorry for the mis-information.


>> Mark
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> Ok, if that is so easy, it should be done. I am developing an online
> game, in which the player dont send messages very often (max: ten
> messages per minute), but is is very important to get the messages of
> other players very fast. Thats why I want to use websockets. But now it
> would be sad, if I need multiple tomcat instances only for connection
> handling although the process handling itself is not very complicated
> (cpu and memory intensive).
> Thank you,
> Chris
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message