[
https://issues.apache.org/jira/browse/AXIS2-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503261
]
Jaliya Ekanayake commented on AXIS2-1363:
-----------------------------------------
This is definitely a bug and against HTTP. We (Eran,Deepal, Srinath, Amila and
Jaliya) this happens because we are not closing the output stream of the
incoming connection at the message receiver, yet write 202 Accepted, and then
write the response again with 200 to the same output stream.
Possible Solution:
Make addressing must for this message receiver and check <wsa:ReplyTo> header
at the message receiver.
If it is anonymous we raise and exception
else write 202 Accepted to the output stream and send the reply to the reply to
address.
> RPCInOutAsyncMessageReceiver mis behaviour
> ------------------------------------------
>
> Key: AXIS2-1363
> URL: https://issues.apache.org/jira/browse/AXIS2-1363
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.1
> Reporter: Ruwan Linton
> Assignee: Thilina Gunarathne
> Priority: Blocker
>
> RPCInOutAsyncMessageReceiver is sending 202 Accepted HTTP response when a
> request comes and then send the actual response with the 200 OK HTTP
> response. This is correct if the client is listning in a seperate channel for
> the response.
> But if the client is listning for the response in the same channel this
> scenario is not going to work and that is why I got the exception in the
> AXIS2 1357. In this case client is trying to get the message of the 202
> Accepted response and throws NPE since it doesn't posses any message body.
>
> For the clarity I am attaching the TCPMon out put:
> request:
> POST /axis2-1.1-RC1/services/test HTTP/1.1
> SOAPAction: ""
> User-Agent: Axis2
> Host: 127.0.0.1
> Transfer-Encoding: chunked
> Content-Type: text/xml; charset=UTF-8
> 112
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> <soapenv:Header />
> <soapenv:Body>
> <example1:getName
> xmlns:example1="http://service.test.messageReciever.axis2.apache.org/xsd"; />
> </soapenv:Body>
> </soapenv:Envelope>0
> response:
> HTTP/1.1 202 Accepted
> Server: Apache-Coyote/1.1
> Set-Cookie: JSESSIONID=DD629528CC78F40E98858EFF0E85A164;
> Path=/axis2-1.1-RC1
> Content-Type: text/xml;charset=UTF-8
> Content-Length: 0
> Date: Fri, 13 Oct 2006 05:10:41 GMT
> HTTP/1.1 200 OK
> Server: Apache-Coyote/1.1
> Content-Type: text/xml;charset=UTF-8
> Transfer-Encoding: chunked
> Date: Fri, 13 Oct 2006 05:10:51 GMT
> 15a
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> <soapenv:Header />
> <soapenv:Body>
> <ns:getNameResponse
> xmlns:ns="http://service.test.messageReciever.axis2.apache.org/xsd";>
> <ns:return>asasas</ns:return>
> <ns:return>sdsds</ns:return>
> </ns:getNameResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> I think the problem is in AbstractInOutAsyncMessageReceiver.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
