Hi Dan, Thanks for the response. I followed your suggestions, but unfortunately, I'm still getting the issue. I've digged a little deeper as to what is going on, and it looks to me that the Exchange reference in the ClientImpl is getting clobbered by the threads. So in the org.apache.cxf.endpoint.ClientImpl::onMessage() method, I see 7 unique Message references being passed in for each of the 7 threads, but for two of the Messages, they share the same Exchanges. Consequently, only 6 exchanges end up getting set to FINISHED and one of the threads (which is likely waiting on a different Exchange) waits until it times out. Any idea as to how this is happening? I'm still trying to understand the CXF code so I'm not sure which class exactly is triggering the OnMessage or how the Exchange is set in the Message in the first place.
-- View this message in context: http://cxf.547215.n5.nabble.com/CXF-port-thread-safety-question-tp5721412p5721481.html Sent from the cxf-user mailing list archive at Nabble.com.
