18:06
À : discuss@restlet.tigris.org
Objet : Re: Premature EOF / Broken Pipe
My real application is still the only place I can reproduce the problem. While
watching the client and server both run within Eclipse I can add one more
observation about the order of events when the exceptions occur
Several days of over night testing showed that my application would still
intermittently fail. Switching the order of the messages just reduced the
incident rate.
--
Timothy.
On Wed, Jul 1, 2009 at 1:52 PM, Timothy Aanerud
taane...@aticonsulting.comwrote:
...
In my actual application I have
@restlet.tigris.org
*Objet :* Re: Premature EOF / Broken Pipe
I tried adding a second resource to my sample application. But it doesn't
fail.
In my actual application I have a scheduled background thread doing a POST
transaction, immediately followed by a GET transaction. The Premature EOF
://www.noelios.com/
http://www.noelios.com
De : Timothy Aanerud [mailto:taane...@aticonsulting.com]
Envoyé : mercredi 1 juillet 2009 20:53
À : discuss@restlet.tigris.org
Objet : Re: Premature EOF / Broken Pipe
I tried adding a second resource to my sample application. But it doesn't fail
~ http://www.noelios.com
*De :* Timothy Aanerud
[mailto:taanerudATaticonsulting.comtaane...@aticonsulting.com]
*Envoyé :* vendredi 19 juin 2009 22:05
*À :* discuss@restlet.tigris.org
*Objet :* Re: Premature EOF / Broken Pipe
No, I haven't tried switching HTTP connectors. I get the same
[mailto:taane...@aticonsulting.com]
Envoyé : vendredi 19 juin 2009 22:05
À : discuss@restlet.tigris.org
Objet : Re: Premature EOF / Broken Pipe
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
and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com
*De :* Timothy Aanerud [mailto:taane...@aticonsulting.com]
*Envoyé :* vendredi 19 juin 2009 22:05
*À :* discuss@restlet.tigris.org
*Objet :* Re: Premature EOF / Broken Pipe
No, I haven't
Hi,
I'm having a communications problem between a client/server application both
using Restlet 1.1.1 (and since upgraded to 1.1.5). The client and server are
both running on Fedora 10, OpenJDK-6 build 14.
The client posts a status resource message to the server to exchange status
information
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=4447dsMessageId=2363562
9 matches
Mail list logo