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.
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.
It is happening only under these circumstances, so this is my latest
assumption. However, I would like to verify if the Request object has
any state after an execution, that prevents it from further executions.
Gregor
------ Original Message ------
From: "Simone Bordet" <[email protected]>
To: "Gregor Jarisch" <[email protected]>; "JETTY user mailing list"
<[email protected]>
Sent: 01/24/2020 7:00:36 PM
Subject: Re: [jetty-users] jetty client timeout when called within
(same) ScheduledExecutorService
>Hi,
>
>On Fri, Jan 24, 2020 at 3:02 PM Gregor Jarisch <[email protected]> wrote:
>>
>> Hi,
>>
>> i am using the jetty client (9.4.26.v20200117).
>>
>> I am using ScheduledThreadPoolExecutor (java11) to execute a callable that
>> makes a http call with the jetty client.
>> When I call the FutureResponseListener.get(), it hangs indefinitely.
>>
>> However, when I call the very same request outside of the executor service
>> (directly), it works like expected.
>>
>> jetty client uses the same executorservice then the executing the callable.
>
>Are you configuring the scheduler with just 1 thread?
>
>--
>Simone Bordet
>----
>http://cometd.org
>http://webtide.com
>Developer advice, training, services and support
>from the Jetty & CometD experts.
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users
