[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-users] jetty client timeout when called within (same) ScheduledExecutorService
|
Hi,
On Sun, Jan 26, 2020 at 12:35 PM Gregor Jarisch <gregor@xxxxxxxxxxx> wrote:
>
> Hi,
>
> > Are you configuring the scheduler with just 1 thread?
> No, 256 actually, so that should not be a problem. It just seems as it is waiting for something forever before actually making a new connection.
HttpClient is fully non-blocking, so it does not wait unless you call
APIs that block.
> Is it problematic to reuse an instance of org.eclipse.jetty.client.api.Request after it had been executed ?
> I have a validator in place that checks httpcode and content and depending on config retries the very same http request.
Yes, don't do that, just create a new Request instance every time.
--
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support
from the Jetty & CometD experts.
