Re: Non-Blocking IO Write Issue

2013-12-29 Thread Daniel Mikusa
On Dec 29, 2013, at 11:45 AM, David Bullock wrote: > Well, the states of those threads look normal enough. Definitely not > a resource starvation issue (which is what it 'feels' like). I guess > some values are getting lost somewhere. > > Just looking at the stacktrace for the onWritePossible

Re: Non-Blocking IO Write Issue

2013-12-29 Thread David Bullock
Well, the states of those threads look normal enough. Definitely not a resource starvation issue (which is what it 'feels' like). I guess some values are getting lost somewhere. Just looking at the stacktrace for the onWritePossible() example though ... I'm not able to trace the same execution p

Re: Non-Blocking IO Write Issue

2013-12-29 Thread Daniel Mikusa
On Dec 23, 2013, at 7:55 PM, David Bullock wrote: > On 24 December 2013 07:58, Daniel Mikusa wrote: >> On Dec 19, 2013, at 8:08 PM, David Bullock >> wrote: >> >>> On 20 December 2013 04:10, Daniel Mikusa wrote: > >> Unfortunately, once this problem starts to occur onWritePossible doesn't g

Re: Non-Blocking IO Write Issue

2013-12-23 Thread David Bullock
On 24 December 2013 07:58, Daniel Mikusa wrote: > On Dec 19, 2013, at 8:08 PM, David Bullock > wrote: > >> On 20 December 2013 04:10, Daniel Mikusa wrote: > Unfortunately, once this problem starts to occur onWritePossible doesn't get > called back. > When I take a thread dump of the code, it

Re: Non-Blocking IO Write Issue

2013-12-23 Thread Daniel Mikusa
On Dec 19, 2013, at 8:08 PM, David Bullock wrote: > On 20 December 2013 04:10, Daniel Mikusa wrote: >> When run, you'll see that it processes some of the requests but fails due to >> a timeout. I've not been able to replicate the other exceptions with the >> unit test though, so those may be

Re: Non-Blocking IO Write Issue

2013-12-19 Thread David Bullock
On 20 December 2013 04:10, Daniel Mikusa wrote: > When run, you'll see that it processes some of the requests but fails due to > a timeout. I've not been able to replicate the other exceptions with the > unit test though, so those may be unrelated. > @WebServlet(asyncSupported = true) >

Non-Blocking IO Write Issue

2013-12-19 Thread Daniel Mikusa
I have a simple servlet which I'm running on Tomcat 8 trunk with Java 7. It's using a non-blocking IO WriteListener to write 8k blocks of static data to the response. The number of blocks it will write is given as a request parameter. When I start out making individual requests to the server (