Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpClient User Discussion" <httpclient-users@hc.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
From: Pete Keyes <PKeyes@starbucks.com>
To: HttpClient User Discussion <httpclient-users@hc.apache.org>
Subject: Re: Using PoolingHttpClientConnectionManager in EJB container
Thread-Topic: Using PoolingHttpClientConnectionManager in EJB container
Thread-Index: AQHQEuLrAkjjzMaIWk6UAPlUr+eO+ZyGLjAA//+wqsOABecqgP//jdc6
Date: Fri, 12 Dec 2014 03:36:29 +0000
Message-ID: <1C240508-731F-449E-84FD-28FA6EB10B97@starbucks.com>
References: <D0AB2479.55289%ronen@zooz.com>
 <CAHwqz=27Jz+r0E8=HzXMGaoRgOmTXcVxfxRhBLLW6Zisbmzuag@mail.gmail.com>
 <1418043622.19866.3.camel@apache.org>
 <73A5D62A-8162-4883-996E-261D13727A82@starbucks.com>,<721ED2A7-CA68-4002-B7A9-F4B30623B020@icloud.com>
In-Reply-To: <721ED2A7-CA68-4002-B7A9-F4B30623B020@icloud.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

The strict "not allowed" rule of EJB3.1 was dropped in EJB3.2 specifically =
because the rule was essentially bogus.=20

By making it sound so ominous with "not allowed" and promised of broken Web=
 Apps it made forced people to use servlets instead and for no "real" reaso=
n.=20

Accordingly EJB3.2 allows WebApps to create and manage threads with no more=
 than a simple "warning: do so wisely" which is always good advice ...  :-)

Sent from my iPhone

> On Dec 11, 2014, at 6:35 PM, Shih-liang Chang <atkinschang@icloud.com> wr=
ote:
>=20
> You can wrapped it in a singleton session bean with bean managed concurre=
ncy annotation and CDI in other session bean.
> Though the thread it created (or maybe there isn't any additional thread =
created, I am not sure) is not managed thread thus not suggested in EE envi=
ronments.
>=20
> Best Regards,
> Atkins
>=20
>> On Dec 9, 2014, at 12:16 AM, Pete Keyes <PKeyes@starbucks.com> wrote:
>>=20
>> A singleton qualifies for concurrent execution by multiple threads in a =
container unless it is write locked.=20
>>=20
>> Sent from my iPhone
>>=20
>>>> On Dec 8, 2014, at 5:01 AM, Oleg Kalnichevski <olegk@apache.org> wrote=
:
>>>>=20
>>>> On Mon, 2014-12-08 at 14:31 +0200, Guri Livne wrote:
>>>> Just to make sure I understand:
>>>> You are saying " effectively renders PoolingHttpClientConnectionManage=
r's
>>>> pooling capabilities almost useless."
>>>>=20
>>>> Because EJBs themselves are in a pool and the threads accessing those =
are
>>>> managed by the J2EE server (So no need to hold a pool per EJB instance=
), or
>>>> do you mean that the PoolingHttpClientConnectionManager itself invokes
>>>> threads and thus not suitable for EJB3.1 spec?
>>>=20
>>> Not, it does not spawn threads by itself. However, without concurrent
>>> request execution PoolingHttpClientConnectionManager has no real
>>> advantages over BasicHttpClientConnectionManager.
>>>=20
>>> Oleg
>>>=20
>>>=20
>>>=20
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
>>> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>>=20
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
>> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> For additional commands, e-mail: httpclient-users-help@hc.apache.org
>=20

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org