On Dec 23, 2013, at 7:55 PM, David Bullock david.bull...@machaira.com.au
wrote:
On 24 December 2013 07:58, Daniel Mikusa dmik...@gopivotal.com wrote:
On Dec 19, 2013, at 8:08 PM, David Bullock david.bull...@machaira.com.au
wrote:
On 20 December 2013 04:10, Daniel Mikusa
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
On Dec 29, 2013, at 11:45 AM, David Bullock david.bull...@machaira.com.au
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
On Dec 19, 2013, at 8:08 PM, David Bullock david.bull...@machaira.com.au
wrote:
On 20 December 2013 04:10, Daniel Mikusa dmik...@gopivotal.com 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
On 24 December 2013 07:58, Daniel Mikusa dmik...@gopivotal.com wrote:
On Dec 19, 2013, at 8:08 PM, David Bullock david.bull...@machaira.com.au
wrote:
On 20 December 2013 04:10, Daniel Mikusa dmik...@gopivotal.com wrote:
Unfortunately, once this problem starts to occur onWritePossible
On 20 December 2013 04:10, Daniel Mikusa dmik...@gopivotal.com 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.
