The assertion can only be reached after the message has been received by the endpoint. The weird thing is that the assertion just before checks that the messagesSent metric has increased and that check doesn't fail. I tried yesterday to figure out what could cause that behavior, but I don't have a clue yet.
The testkit actually records a large amount of debugging information. That information should be accessible in Hudson's workspace, but since I don't have an account, I can't access it. I was planning to modify the pom.xml for the synapse-transport module so that it attaches a ZIP with these logs (in a Maven profile that would only be activated on the build server). This would give anybody the opportunity to download them from Hudson for inspection. Andreas On Thu, Nov 6, 2008 at 11:36, Asankha C. Perera <[EMAIL PROTECTED]> wrote: > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
