users@jersey.java.net

Re: [Jersey] Thread waits indefinitely using Apache HTTP based Jersey Client[WAS]Re: Problem switching to ApacheHttpClient in Jersey 1.0.2

From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
Date: Fri, 20 Feb 2009 11:54:30 +0100

On Feb 20, 2009, at 11:44 AM, Imran M Yousuf wrote:

> On Fri, Feb 20, 2009 at 3:19 PM, Paul Sandoz <Paul.Sandoz_at_sun.com>
> wrote:
>> Hi Imran,
>> It appears i did not receive you last email on this thread, i
>> dunno, but i
>> found i by browsing the archive.
>> You said:
>>
>> Hmm, a valid point, IMHO, this behavior is coherent with that JDBC
>> Connection and JPA/Hibernate Session. IMHO, we might just add it to
>> the
>> JavaDoc's or release notes explicitly as if developers migrate from
>> Jersey
>> default Client to ApacheHttpClient they might face it.
>>
>> I added something to the ApacheHttpClient JavaDoc,
>> Paul.
>
> Thanks for the documentation. I had a question regarding this, when
> can I expect the SNAPSHOT to be available for testing?
>

Now, it is continuously built. Usually, if all goes well and there are
no test failures or networking issues, Hudson pushes out new artifacts
about 1 to 2 hours after a commit.

You can see results here:

  http://hudson.glassfish.org/job/Jersey/

Paul.