axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yuanfeng Zhang <yuanfeng.zh...@gmail.com>
Subject Soap Message whit MTOM enabled Can't Work
Date Mon, 30 Mar 2009 06:31:01 GMT
Hi,
    We get the latest axis2c source code from svn, built it with Visual C++
2008,  and run it as a client on Window XP platform. It really works
without MTOM enabled. BUT, when it is set to be MTOM enabled, it cannot work
at all.

The server side is Apache2 server with axis2c module, and the error message
is that "[Mon Mar 30 10:02:42 2009] [critical] soap_builder.c(852) SOAP
message does not have a SOAP envelope element". We also captured http
packets sent out from client side, the related messages are list below.

We didn't find this problem in axis2c1.5, it seems a new problem. Please
help check it. Thanks!


POST /axis2/services/bss_service_trs HTTP/1.1

User-Agent: Axis2C/1.6.0

Transfer-Encoding: chunked

Content-Type: multipart/related;
boundary=MIMEBoundarye9260144-753c-43c1-9da4-27c45d19ba4e;
type="application/xop+xml";
start="<0.29bca945-2a86-4769-8bbf-38eaf6d42ea8@apache.org>";
start-info="application/soap+xml"; charset="UTF-8"

Host: 10.24.2.2:8080



32

--MIMEBoundarye9260144-753c-43c1-9da4-27c45d19ba4e

2





b2

content-transfer-encoding: binary

content-id: <0.29bca945-2a86-4769-8bbf-38eaf6d42ea8@apache.org>

content-type: application/xop+xml;charset=UTF-8;type="application/soap+xml";



2





1b5

<soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><operation
name="download_chunk" version="version01"><request_head
req_sequence="1" password="123456789"
user_name="yuanfeng.zhang@gmail.com"><host_id>49</host_id></request_head><download_chunk
MD5="baf08d6d5abbed726c6d9da2617b5175"
storage_key="baf08d6d5abbed726c6d9da2617b5175.DAT"></download_chunk></operation></soapenv:Body></soapenv:Envelope>



34

--MIMEBoundarye9260144-753c-43c1-9da4-27c45d19ba4e--

0



HTTP/1.1 500 Internal Server Error

Date: Mon, 30 Mar 2009 02:06:33 GMT

Server: Apache/2.2.3 (Red Hat)

Connection: close

Transfer-Encoding: chunked

Content-Type: multipart/related;
boundary=MIMEBoundary64686728-1ccf-1de1-2da5-001e4fd3ad50;
type="application/xop+xml";
start="<0.64686746-1ccf-1de1-2da6-001e4fd3ad50@apache.org>";
start-info="application/soap+xml"; charset="UTF-8"



2d4

--MIMEBoundary64686728-1ccf-1de1-2da5-001e4fd3ad50

content-transfer-encoding: binary

content-id: <0.64686746-1ccf-1de1-2da6-001e4fd3ad50@apache.org>

content-type: application/xop+xml;charset=UTF-8;type="application/soap+xml";



<soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Header></soapenv:Header><soapenv:Body><soapenv:Fault><soapenv:Code><soapenv:Value>soapenv:Sender</soapenv:Value></soapenv:Code><soapenv:Reason><soapenv:Text
xmlns:xml="http://www.w3.org/XML/1998/namespace" xml:lang="en">SOAP
message does not contain a SOAP envelope
element</soapenv:Text></soapenv:Reason></soapenv:Fault></soapenv:Body></soapenv:Envelope>

--MIMEBoundary64686728-1ccf-1de1-2da5-001e4fd3ad50--

0

Mime
View raw message