Re: [jetty-user] Jetty request recycling
Simone Bordet <[email protected]> Fri, 21 Sep 2012 17:39:15 +0200
| Newsgroups | gmane.comp.java.jetty.support |
|---|---|
| Message-ID | <CAFWmRJ16a=zZbNrSSabc=HXEtB0RvFAUQtB6EUo1oY3L9kQUhQ@mail.gmail.com> |
Hi, On Fri, Sep 21, 2012 at 3:41 PM, Silvio Bierman <[email protected]> wrote: > Hello all, > > Can someone sched some light on when and how Jetty recycles request objects? > Are the objects guaranteed to stay valid until for example a doGet or doPost > has returned? I seem to have some cases where request information seems to > change during execution of a doPost. Requests are recycled per-connection, after the response is complete. If you call request.startAsync() and return from doGet() or doPost(), the request is kept alive until the request is completed (which may happen a number of invocations to doGet() or doPost() later, depending what your application does). If you have a reproducible test case, file a bugzilla, and we'll look at it. Simon -- http://cometd.org http://webtide.com Developer advice, services and support from the Jetty & CometD experts. ---- Finally, no matter how good the architecture and design are, to deliver bug-free software with optimal performance and reliability, the implementation technique must be flawless. Victoria Livschitz --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email