No, I haven't tried switching HTTP connectors. I get the same failures for both HTTP and HTTPS. In another experiement, I changed the client message frequency to ~1 second intervals and at this rate on both Windows XP and Fedora10/Linux show now problems with the server running on Fedora.
The various frequencies and failure rates: 1 second == no problems 1.5 seconds == ~25% failure rate 5 seconds == ~25% failure rate 10 seconds == ~3% failure rate 180 seconds == >0.5%, if any failures I'll switch the HTTP connectors out one at a time and see what happens. -- Timothy Aanerud On Fri, Jun 19, 2009 at 2:02 PM, Jerome Louvel <[email protected]>wrote: > Hi Timothy, > > This looks like a bug to me. Have you tried with different Restlet HTTP > connectors (such as Jetty on the server-side and Apache HTTP client)? > > If you could send us a simple standalone test case, we could easily debug > what's going bad. > > Best regards, > Jerome Louvel > -- > Restlet ~ Founder and Lead developer ~ http://www.restlet.org > Noelios Technologies ~ Co-founder ~ http://www.noelios.com > > > -----Message d'origine----- > De : Timothy Aanerud [mailto:[email protected]] > Envoyé : vendredi 19 juin 2009 18:18 > À : [email protected] > Objet : RE: Premature EOF / Broken Pipe > > As a test, I moved the client code to a Windows XP machine. With a five > second update rate it fails regularly too, with the same exceptions and > stack traces. > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=23635 > 62 > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2363638 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2363663
