On Jan 13, 2014, at 7:13 AM, Jose María Zaragoza <[email protected]> wrote:

> <?xml version="1.0" encoding="utf-8" standalone="yes"?>
> <SOAP-ENV:Envelope 
> xmlns:add="http://schemas.xmlsoap.org/ws/2004/08/addressing";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";>
> <SOAP-ENV:Header>
> <add:MessageID>urn:uuid:8e51d90c-1013-48c6-bd74-b41751f3e0a7</add:MessageID>
> </SOAP-ENV:Header>
> <SOAP-ENV:Body>
> <ns:processResponse
> xmlns:ns="urn:com:external:types">
> <ns:resultCode>0</ns:resultCode>
> <ns:ldata>
> <ns:ldata2>
> <ns:data>
> <ns:id>1237</ns:id>
> </ns:data>
> </ns:ldata2>
> </ns:ldata>
> </ns:processResponse>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
> 
> I  don't see any “RelatesTo” header in response. Should it ?

Yes.

Per the WS-Addressing Spec:
/wsa:RelatesTo
This OPTIONAL (repeating) element information item contributes one abstract 
[relationship] property value, in the form of a (URI, QName) pair. The 
[children] property of this element (which is of type xs:anyURI) conveys the 
[message id] of the related message. This element MUST be present if the 
message is a reply.

Note the last sentence.   For a reply message, the RelatesTo header must be 
there.


> 
> 2014-01-13 12:58:38.779 [http-8080-2] WARN  [ContextUtils] [doLog] -
> WS-Addressing - failed to retrieve Message Addressing Properties from
> context
> 2014-01-13 12:58:38.780 [http-8080-2] WARN  [ContextUtils] [doLog] -
> WS-Addressing - failed to retrieve Message Addressing Properties from
> context
> 2014-01-13 12:58:39.799 [http-8080-2] WARN  [ContextUtils] [doLog] -
> WS-Addressing - failed to retrieve Message Addressing Properties from
> context

These are showing that the RelatesTo header wasn’t there or similar as it 
couldn’t correlate the response message to a request.    That is certainly the 
cause of the “leak” as the WS-Addressing stuff is not seeing a proper response 
to the request.


-- 
Daniel Kulp
[email protected] - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Reply via email to