You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Frederic Heem (JIRA)" <ji...@apache.org> on 2008/06/30 17:41:45 UTC

[jira] Commented: (AXIS2C-1213) server returns HTTP/1.1 500 Internal Server Error for In-Only message

    [ https://issues.apache.org/jira/browse/AXIS2C-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609264#action_12609264 ] 

Frederic Heem commented on AXIS2C-1213:
---------------------------------------

Please note that the nofity client works. 
Here are the difference between the 2:
* SOAPAction is set to "" in one, in notify, this field is not present. Why is set to "" at the first place ? 
* The content type is text/xml and application/soap+xml in notify. 
* soap 11 is used in the first case, soap12 in the second. How WSDL2C can be told to use soap 12 ?

Here is the conversation:
 POST /axis2/services/notify HTTP/1.1
User-Agent: Axis2C/1.4.0
Content-Length: 426
Content-Type: application/soap+xml;charset=UTF-8
Host: localhost:9090

<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:To>http://localhost:9090/axis2/services/notify</wsa:To><wsa:Action>notify</wsa:Action><wsa:MessageID>8044fb10-46b9-1dd1-2223-0014c2e176e7</wsa:MessageID></soapenv:Header><soapenv:Body><m:notify xmlns:m="http://example.org/notify">notify5</m:notify></soapenv:Body></soapenv:Envelope>HTTP/1.1 202 Accepted
Date: Mon Jun 30 16:30:43 2008 GMT
Server: Axis2C/1.4.0 (Simple Axis2 HTTP Server)

> server returns HTTP/1.1 500 Internal Server Error for In-Only message
> ---------------------------------------------------------------------
>
>                 Key: AXIS2C-1213
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1213
>             Project: Axis2-C
>          Issue Type: Bug
>    Affects Versions: Current (Nightly)
>         Environment: linux fc6
>            Reporter: Frederic Heem
>            Priority: Blocker
>
> After upgrading from svn, In-Only messages stop working correctly: 
> * the server returns HTTP/1.1 500 Internal Server Error
> * the client returns successfully even though the server returns an error:
> Here the conversation between and server:
> POST /axis2/services/zigbee HTTP/1.1
> User-Agent: Axis2C/1.4.0
> SOAPAction: ""
> Content-Length: 507
> Content-Type: text/xml;charset=UTF-8
> Host: localhost:9090
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:To>http://localhost:9090/axis2/services/zigbee</wsa:To><wsa:Action>PermitJoining</wsa:Action><wsa:MessageID>5b6a6c86-46b8-1dd1-3722-0014c2e176e7</wsa:MessageID></soapenv:Header><soapenv:Body><n:PermitJoiningParam xmlns:n="http://www.telsey.com/DPWS/2008/03/Zigbee"><n:permitDuration>50</n:permitDuration></n:PermitJoiningParam></soapenv:Body></soapenv:Envelope>
> HTTP/1.1 500 Internal Server Error
> Date: Mon Jun 30 16:22:31 2008 GMT
> Server: Axis2C/1.4.0 (Simple Axis2 HTTP Server)
> Content-Type: text/xml;charset=UTF-8
> Content-Length: 370
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header></soapenv:Header><soapenv:Body><soapenv:Fault><faultcode>soapenv:Sender</faultcode><faultstring>NULL parameter was passed when a non NULL parameter was expected</faultstring><detail><TestServiceError></TestServiceError></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>

-- 
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org