11:21 a.m.
Would like to inquire about the current state of thead-safety of the RESTEasy
implementation of the JAX-RS javax.ws.rs.client.Client. There seems to be a discussion
about how to get this into the spec, here: https://github.com/jakartaee/rest/issues/494
Apart from not yet being in the current spec, is there an "official" statement
how RESTEasy handles this now? Can we already rely on the Client being thread-safe or
should we keep a ThreadLocal for clients?
Thanks
John
11:18 a.m.
Hi John,
I would need to look in more detail, but I think the answer is it depends
:) The client does use ThreadLocal's for its configuration. However, with
something like MP Context Propagation that should be able to handle that.
If you're running in newer versions of WildFly it should work as well if
you use Jakarta EE Concurrency for threads.
What container or environment are you running in?
On Wed, May 4, 2022 at 9:28 AM John Ulrik <ujay68(a)gmail.com> wrote:
Would like to inquire about the current state of thead-safety of the
RESTEasy implementation of the JAX-RS javax.ws.rs.client.Client. There
seems to be a discussion about how to get this into the spec, here:
https://github.com/jakartaee/rest/issues/494
Apart from not yet being in the current spec, is there an "official"
statement how RESTEasy handles this now? Can we already rely on the Client
being thread-safe or should we keep a ThreadLocal for clients?
Thanks
John
_______________________________________________
resteasy mailing list -- resteasy(a)lists.jboss.org
To unsubscribe send an email to resteasy-leave(a)lists.jboss.org
--
James R. Perkins
JBoss by Red Hat
9:25 a.m.
Thanks, James. Currently running in JBoss EAP 7.3.10, among others (not my choice to make,
actually), but this is a more general question. Sounds like I should make a ThreadLocal of
Clients to be safe. Also this is not about universal, formal thread-safety but whether I
can use a once-initialized Client instance, with no configuration changes made further on,
in more than one thread concurrently (typically servlet request threads of the container).
5:48 p.m.
Hi John,
I would probably use CDI over using a ThreadLocal. That said, I did a
little testing with using a client in a new thread and did not have any
issues in EAP 7.3.8. The Client itself should be thread-safe. The question
would be more is the context setup correctly.
For CDI here's what I've done upstream for RESTEasy 6.1 to allow a client
to be injected. It should work for Jakarta EE 8 too.
https://github.com/resteasy/resteasy/blob/bd243c393e88481b797fb4371c18a44...
On Sun, May 8, 2022 at 7:25 AM John Ulrik <ujay68(a)gmail.com> wrote:
Thanks, James. Currently running in JBoss EAP 7.3.10, among others
(not my
choice to make, actually), but this is a more general question. Sounds like
I should make a ThreadLocal of Clients to be safe. Also this is not about
universal, formal thread-safety but whether I can use a once-initialized
Client instance, with no configuration changes made further on, in more
than one thread concurrently (typically servlet request threads of the
container).
_______________________________________________
resteasy mailing list -- resteasy(a)lists.jboss.org
To unsubscribe send an email to resteasy-leave(a)lists.jboss.org
--
James R. Perkins
JBoss by Red Hat
1041
days inactive
1049
days old
3 comments
2 participants
participants (2)
-
James Perkins -
John Ulrik