Hi Larry
On 2013-01-24 00:08, Larry Presswood wrote:
We are trying to track down an issue where a request on one thread is
getting the wrong reply..
I suspect the issue is not in CXF as we are not doing anything that
is
on the website which would not be thread safe. Per my understanding
CXF uses ThreadLocals to deal with concurrency
This occurs in 2.5.2 and 2.7.0 as I said I am in doubts its a CXF
problem
In the logging interceptor I see ID: 2 both outbound and inbound like
below
INFO org.apache.cxf.services.common_bmx.bmx.bmxPort - Outbound
Message
---------------------------
ID: 2
Address: http://oma3amtsdevl3:13771/wsdl/
Encoding: UTF-8
Http-Method: POST
Content-Type: text/xml
Headers: {Accept=[*/*], SOAPAction=["bmxInit"]}
--------------------------------------
INFO org.apache.cxf.services.common_bmx.bmx.bmxPort - Inbound Message
----------------------------
ID: 2
Response-Code: 200
Encoding: UTF-8
Content-Type: text/xml; charset=utf-8
Headers: {Content-Length=[2061], content-type=[text/xml;
charset=utf-8]}
The above matched up correctly and can I assume that a Given ID is
generated for each request and does that correlate to a new http
connection ie a new socket? So I can be pretty sure that the reply i
get back for the same ID had to have come from our Server on the same
socket or http connection? I removed the payload to hide my clients
name
As far as I know this logging ID is set for the underlying exchange.
Our server is custom product written in C++ that handles soap so it
could be a defect there but i am trying to locate where the problem
is
and at this point i dont have compelling evidence that its not CXF
First thing I would do is tcpdump'ing the message exchange to check if
the server endpoint is sending the expected message back to your CXF
client.
cheers
Thanks
Sent from iCloud
--
Oliver Moser
