Andreas
There is an interesting random failure in the HTTP NIO test cases:
junit.framework.AssertionFailedError: No increase in bytes sent
This would mean that the transport sender in some cases doesn't update
the metrics correctly. Any idea?
I noticed this too.. let me try to see whats happening, ..
My suspicion is that the assert is called before actual send takes place
(asynchronously). Also, this seems to fail for HTTP 1.0 case, where we
buffer the message before sending (to calculate the Content-Length)
Thus a workaround would be to check if the bytesSent increased, and if
not, wait a few milliseconds (maybe 200) and then check again before
failing.. however, this is just a guess since I am not familiar with the
test kit codebase..
Could you fix this with the above or a better solution?
asankha
--
Asankha C. Perera
http://adroitlogic.org
http://esbmagic.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
