7

I'm using CXF to generate SOAP client classes. In the CXF documentation, they write

Are JAX-WS client proxies thread safe?

Official JAX-WS answer: No. According to the JAX-WS spec, the client proxies are NOT thread safe. To write portable code, you should treat them as non-thread safe and synchronize access or use a pool of instances or similar.

CXF answer: CXF proxies are thread safe for MANY use cases. The exceptions are:

(I'm omitting their description of these use cases)

For most "simple" use cases, you can use CXF proxies on multiple threads. The above outlines the workarounds for the others.

Does anyone have any contrary experiences? Encountered multi-threading issues that aren't described in their faq? Or is their description accurate and they are basically safe to use?

Community
  • 1
  • 1
Eyal
  • 3,412
  • 1
  • 44
  • 60
  • What exactly does this mean? Does this mean that Client Proxies **as generated by CXF `wsdl2java`** are (mostly) thread-safe, or do you need to use any actual CXF APIs in your client program? – Maarten Boekhold Mar 07 '13 at 06:38
  • @MaartenBoekhold I meant the generated client proxies. – Eyal Mar 07 '13 at 23:20

2 Answers2

6

We recently ran into similar discussion in our project. As specified in the FAQ you are referring to, except for the features that modify HTTP conduit on the fly (ex: session management and failover features), the CXF client proxy is thread safe. So if you do not use these features then it is okay to share the client proxy between threads.

Srimathi
  • 247
  • 1
  • 4
1

You're probably referring to runtime, but I don't think configuration time is meant to be threadsafe. I believe I've seen a race condition in JettyHTTPServerEngineFactory.

In a test harness we bring up multiple unrelated SOAP servers and when they share a Bus there's a potential for a race condition if multiple threads attempt to add JettyHTTPServerEngine instances at the same time. The specific race condition is in setTLSServerParametersForPort(), which you call when you want to use HTTPS for a port. That method adds elements to a HashMap with no locking.

I guess the reason others don't encounter this is that most people configure CXF via configuration files, and it's rare to have multiple ports/Jetty servers in one process.

David Gladfelter
  • 4,175
  • 2
  • 25
  • 25
  • And it turns out a newer version of CXF fixes this particular race condition, but I haven't seen a definitive contract on threading in CXF's documentation. Also, the map is static so the race condition in the older version happens regardless of the Bus. – David Gladfelter Aug 18 '14 at 01:48