axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Chen (JIRA)" <>
Subject [jira] Issue Comment Edited: (AXISCPP-1035) Foreign soap server replying HTTP 500 masked by misleading Axis error
Date Mon, 10 Dec 2007 23:31:43 GMT


mwc_tonesoft edited comment on AXISCPP-1035 at 12/10/07 3:31 PM:


There is no movement on this and many other issues. Please give me an update.


      was (Author: mwc_tonesoft):

There is no movement on this and many other issues. Please give me an update.

By the way, I wan to point out that, if you look closely at the debug output in the above
description, right after HTTP header "Connection: close\r\n\r\n", there is an extra line of
"217\r\n" before the start of the "<?xml " tag.

I believe this extra line of "217\r\n" was erroneously generated by the server-side web service
engine (Cisco Call Manager 6.01, probably running an older version of Axis for Java).  This
extra line most likely caused Axis-C to issue the AxisSoapException, because Axis-C cannot
tolerate extra text before the "<?xml " tag.

A bug fix is needed so that Axis-C can be more robust by ignoring extra text before the "<?xml
" tag.

> Foreign soap server replying HTTP 500 masked by misleading Axis error
> ---------------------------------------------------------------------
>                 Key: AXISCPP-1035
>                 URL:
>             Project: Axis-C++
>          Issue Type: Bug
>          Components: Transport (axis3)
>    Affects Versions:  1.6 Final
>         Environment: Linux (Intel x86)
>            Reporter: Michael Chen
>            Assignee: nadir amra
> Axis-CPP 1.6 revision 565851 (trunk as of 08/14/2007):
> If a foreign (not Axis) Soap server reply "HTTP 500 Internal server error" with a proper
soap envelop containing the SoapFault, Axis throws a misleading exception:
>     AxisSoapException: Cannot deserialize the requested element.
> Granted that this foreign server sent back a reply that does not match its WSDL. However,
Axis should not discard the perfectly legitimate SoapFault message.
> The full gdb print out of the HTTP reply from this Soap server (Cisco Call Manager 6.01)
> Breakpoint 2, HTTPTransport::readHTTPHeader (this=0x8edfd18)
>     at /u1/opt/axis-c-trunk/src/transport/axis3/HTTPTransport.cpp:1687
> 1687        if ( m_iResponseHTTPStatusCode != 500
> (gdb) print m_iResponseHTTPStatusCode
> $1 = 500
> (gdb) x/6s m_pszRxBuffer
> 0x8edfe38:       "HTTP/1.1 500 Internal Server Error\r\nServer: Apache-Coyote/1.1\r\nSet-Cookie:
JSESSIONIDSSO=85CA147A8921D3ABF00646668D4781D9; Path=/\r\nSet-Cookie: JSESSIONID=8F1F8C66A6208A5638619BF9D6EDE3EC;
> 0x8edff00:       "emandService; Secure\r\nSet-Cookie:\r\nContent-Type:
text/xml;charset=utf-8\r\nTransfer-Encoding: chunked\r\nDate: Sat, 14 Apr 2007 03:26:25 GMT\r\nConnection:
> 0x8edffc8:       "<?xml version=\"1.0\" encoding=\"UTF-8\"?><soapenv:Envelope
xmlns:soapenv=\"\" xmlns:xsd=\"\"
> 0x8ee0090:       "ma-instance\"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server.userException</faultcode><faultstring>java.rmi.RemoteException:
No file found within the specified time range</faultstring><detail><"...
> 0x8ee0158:       "ns1:hostname xmlns:ns1=\"\">TSC-CCM1</ns1:hostname></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>\r\n"
> 0x8ee01e2:       ""

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:
For additional commands, e-mail:

View raw message