Jerome Louvel noelios.com> writes:
>
>
> Hi Bruce,
>
> Great news!
>
> Regarding the 40s delay I'm puzzled... Did you monitor the state of sockets?
> Are they all closed in a timely manner?
>
> Did you try using a profiler to detect which part of the code actually
> causes the delay?
>
>
imely manner?
>
> Did you try using a profiler to detect which part of the code actually
> causes the delay?
>
> Best regards,
> Jérôme Louvel
> --
> Restlet ~ Founder and Lead developer ~ http://www.restlet.org
> Noelios Technologies ~ Co-founder ~ http://www.noelios.com
Jerome Louvel noelios.com> writes:
>
>
> Hi Bruce,
>
> Great news!
>
> Regarding the 40s delay I'm puzzled... Did you monitor the state of
sockets?
> Are they all closed in a timely manner?
>
> Did you try using a profiler to detect which part of the code actually
> causes the delay?
ROTECTED] De la part de Bruce Lee
Envoyé : lundi 29 septembre 2008 16:40
À : discuss@restlet.tigris.org
Objet : Re: Random Grizzly IOException
Hi Jerome,
My environment is as follows:
OS: Windows XP Pro SP2
JVM:
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Client VM
eveloper ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com
-Message d'origine-
De : news [mailto:[EMAIL PROTECTED] De la part de Bruce Lee
Envoyé : vendredi 26 septembre 2008 18:39
À : discuss@restlet.tigris.org
Objet : Re: Random Grizzly IOException
Hi J
com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:169)
Sep 26, 2008 12:35:53 PM com.noelios.restlet.LogFilter afterHandle
Regards,
Bruce Lee wrote:
Hi Jerome,
Thanks a lot for the timely fix! I'll be looking forward to test out the
1.1RC2.
Regards,
Jerome Louvel wrote:
Hi Bruce,
Thanks a lot for sh
-founder ~ http://www.noelios.com
-Message d'origine-
De : news [mailto:[EMAIL PROTECTED] De la part de Bruce Lee
Envoyé : vendredi 19 septembre 2008 20:43
À : discuss@restlet.tigris.org
Objet : Re: Random Grizzly IOException
Hi Jerome,
Sorry to took so long to reply as I got side tracked with
are more adventurous!
Best regards,
Jerome
-Message d'origine-
De : news [mailto:[EMAIL PROTECTED] De la part de Bruce Lee
Envoye : mercredi 2 juillet 2008 22:02
A : discuss@restlet.tigris.org
Objet : Random Grizzly IOException
Hi,
I'm testing out grizzly connector with the 1.1M
Hi,
Thanks for the information, I guess we will have to wait until Restlet 1.1
becomes stable so we can try out the feature.
Regards,
Hi,
I'm trying to setup a host with the following address but have different
certificate.
https://localhost:8080
https://localhost:8082
My problem is although the server connectors seems to start correctly, when I
check the certificate for each of the site, it shows the same certificate. I'm
no
Hi,
I'm testing out grizzly connector with the 1.1M4 built and I noticed that for
requests takes a bit longer to generate the report, sometimes the following
exceptions occurs:
Jul 2, 2008 4:01:11 PM com.noelios.restlet.http.HttpServerConverter commit
INFO: Exception intercepted
java.io.IOExcepti
Jerome Louvel noelios.com> writes:
>
> Also, the way the Jetty connector for Restlet works doesn't require the
> costly Servlet container layer, it's using a lower level Jetty API. So
> performance are very good and could be compared to those of the Grizzly
> connector for Restlet.
Hi Jerome,
>
> Hi Bruce,
>
> Currently, the Grizzly connector is not ready for production. There are a
> couple of outstanding bugs that we need to fix. We'd like to run some
> benchmarks as well before final 1.1 release.
>
> However, even if 1.1 release should be ready for production, it would still
> be
Hi,
Currently my application is designed as a servlet inside Tomcat, which
was working fine but we would like to move away from Tomcat to have
better control on on the application life cycle is managed. I have
tried using the latest Restlet (1.1M4) with the Grizzly and the
migration was easy as sw
14 matches
Mail list logo
