On 03/13/2013 01:20 AM, Mark Thomas wrote:
And an infinite loop is entered. I believe I can fix this by changing how I do the buffering in WebSocket so I don't end up having to write short 4 byte chunks. I have been meaning to do this for a while anyway. That said, this does look like an issue with APR/native and SSL. Thoughts?
The only solution would be to have some sort of different retvals for real EAGAIN (network layer) and case when encryption cannot be made (protocol layer) due to insufficient data. That is if OpenSSL returns some distinct error in such case. Perhaps the internal buffering would be a way to go, cause we poll only on network events, and if that's satisfied we need a different kind of queue for filling the minimum write buffer. I'll try to dig and see if we can distinguish between those different EAGAIN retvals. Regards -- ^TM --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
