Well, I finally figured out the problem. It seems that unique message ids are required when sending out multi-threaded requests with CXF. I tracked down where the ExchangeImpl was getting overwritten, and it was happening after the message is received and the interceptors are being applied. The MapCodec interceptor correlates the response with the request via the message id, and since they were not unique, the correlation was matching the response with the wrong request. Anyways, ensuring the message ids are unique seemed to have solved my problem.
-- View this message in context: http://cxf.547215.n5.nabble.com/CXF-port-thread-safety-question-tp5721412p5721494.html Sent from the cxf-user mailing list archive at Nabble.com.
