I haven't been able to reliably reproduce it yet. Seems to happen more on
slower machines. Sometimes I see underlying log messages that indicate
problems, but nothing consistent. I'm headed up against a release and
switching to HTTPClient fixed the issue (it's been running regularly for a day
The 1001 error proved to be caused by a ClassCastException in my case.
I forgot to change the object type for custom headers from Form to
Series. The errors were gone after fixing this.
Cheers,
Arjohn Kampman
On 23/04/2012 10:12, Jerome Louvel wrote:
> Hi Arjohn,
>
> We are looking for ways to co
t.com
http://twitter.com/#!/jlouvel
-Message d'origine-
De : Arjohn Kampman [mailto:arjohn.kamp...@aduna-software.com]
Envoyé : lundi 23 avril 2012 09:56
À : discuss@restlet.tigris.org
Objet : Re: 2.1 Status of Connectors
Hi Jerome,
I'm reproducably seeing this "commun
r, use Jetty or Simple for now in production.
>
> Best regards,
> Jerome
> --
> http://www.restlet.com
> http://twitter.com/#!/jlouvel
>
>
> -Message d'origine-
> De : Grant [mailto:gsing...@apache.org]
> Envoyé : dimanche 22 avril 2012
ction.
Best regards,
Jerome
--
http://www.restlet.com
http://twitter.com/#!/jlouvel
-Message d'origine-
De : Grant [mailto:gsing...@apache.org]
Envoyé : dimanche 22 avril 2012 20:32
À : discuss@restlet.tigris.org
Objet : 2.1 Status of Connectors
http://wiki.restlet.org/docs_2.1/13-
http://wiki.restlet.org/docs_2.1/13-restlet/27-restlet/325-restlet/37-restlet.html
is leaving me a bit confused as to what I should be using for client
connectors. I've been fighting with intermittent "communication errors (1001)"
over HTTP that had all the symptoms of timeouts or other problem
6 matches
Mail list logo