axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ruwan Linton (JIRA)" <>
Subject [jira] Created: (AXIS2-1363) RPCInOutAsyncMessageReceiver mis behaviour
Date Fri, 13 Oct 2006 05:35:39 GMT
RPCInOutAsyncMessageReceiver mis behaviour

                 Key: AXIS2-1363
             Project: Apache Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: core
    Affects Versions: 1.1
            Reporter: Ruwan Linton
            Priority: Critical

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:


POST /axis2-1.1-RC1/services/test HTTP/1.1

SOAPAction: ""

User-Agent: Axis2


Transfer-Encoding: chunked

Content-Type: text/xml; charset=UTF-8


<?xml version='1.0' encoding='UTF-8'?>
   <soapenv:Envelope xmlns:soapenv="">
      <soapenv:Header />
         <example1:getName xmlns:example1=""


                     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


                     <?xml version='1.0' encoding='UTF-8'?>
                        <soapenv:Envelope xmlns:soapenv="">
                           <soapenv:Header />
                              <ns:getNameResponse xmlns:ns="">

I think the problem is in AbstractInOutAsyncMessageReceiver.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message