While the original messsage is long, it doesn't contain the critical information.
Exactly what combination of API and Spring (or lack of Spring) are you using to create the clients? What objects are you sharing between threads? On Wed, Mar 11, 2009 at 9:32 AM, Cornel Masson <[email protected]> wrote: > I saw that 'thread.local.request.context' property in the FAQ > (http://cxf.apache.org/faq.html#FAQ-FrequentlyAskedQuestions) under "Are > JAX-WS client proxies thread safe?". However, at the time it seemed to me it > is only necessary to set that if my client code explicitly uses > ((BindingProvider)proxy).getRequestContext(), which it doesn't; or are you > saying that some of the CXF Client code uses it, so you should always set it > to true? > > -Cornel > > > Adrian Corcoran wrote: >> >> There is a CXF property 'thread.local.request.context' that you can >> set to true when instantiating the client that will give each thread >> its own unique request context. This should eliminate your client side >> concurrency issues. >> > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ >
