Hi Mike > Asankha - Thanks for committing the fix. The 'other' means by which this > error comes up, is when I deploy to a server that has active keepalive > requests hitting synapse. Unfortunately I don't know enough about these > requests to link the problem conclusively to that activity, and also > unfortunately, I was unable to run the tests in that particular > environment this weekend. I'll see if I can get on the system tomorrow > night and run tcpdump from there. > The possibility I could think of is a new and valid request coming over a keepalive connection, which is just being closed by Synapse.. the probability of which is low, unless the system is under load. The current fix should work even in that case, but the client will get an error, which may not be perfect, but I think possible options we have is limited.
If possible, leave the tcpdump running and gzip the file once this happens - else you may end up with a huge log file.. You may send the file directly to me as the tcp dump may reveal message data if posted publicly. cheers asankha -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com
