[
https://issues.apache.org/jira/browse/AXIS2-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574841#action_12574841
]
Ruwan Linton commented on AXIS2-3529:
-------------------------------------
Dims,
This causes some issues to Synapse, because synapse NIO transport consider this
200 message as an application POX message (I think this is not wrong according
to the HTTP semantics) and tries to inject to synapse with a default envelope
which results in a loop back. So it is better if we can get this fixed in the
next release.
Ideally it should return 202 Accepted rather than 200 OK
Thanks,
Ruwan
> Axis2 server responds with Http 200 instead of 202 for the request of a dual
> channel invocation
> -----------------------------------------------------------------------------------------------
>
> Key: AXIS2-3529
> URL: https://issues.apache.org/jira/browse/AXIS2-3529
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: nightly
> Environment: winxp, jdk15
> Reporter: Charitha Kankanamge
> Assignee: Deepal Jayasinghe
> Priority: Critical
> Fix For: 1.4
>
>
> In the dual channel service invocation, Axis2 server is expected to respond
> to the request message with http 202. This was working correctly in
> Axis2-1.3. However, server responds with 200 OK for the request in the latest
> nightly builds.
> Steps to reproduce:
> ================
> 1. Deploy a service in Axis2 server
> 2. Write an dual channel async client
> 3. Invoke the service and monitor the message flow using tcpmon
> When you send the request, you will get http 200 as the response code.
--
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]
