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 Re: Soap Message whit MTOM enabled Can't Work
Date Mon, 30 Mar 2009 08:42:45 GMT
it is the same when we run mtom sample...
--------------------------------------------------------------------------------------------------------------------
\client\bin>mtom.exe http://10.24.2.2:8080/axis2/services/bss_serv
ice_trs
log folder C:\Borqs\uDrop\client\axis2c/logs does not exist - log file
mtom.log
is written to . dir
Using endpoint : http://10.24.2.2:8080/axis2/services/bss_service_trs
<ns1:mtomSample xmlns:ns1="http://ws.apache.org/axis2/c/samples/mtom
"><ns1:fileN
ame>test.jpg</ns1:fileName><ns1:image><xop:Include xmlns:xop="
http://www.w3.org/
2004/08/xop/include" href="
cid:1.9971c660-0b4d-44d6-89ad-66392b09d352@apache.org<cid%3A1.9971c660-0b4d-44d6-89ad-66392b09d352@apache.org>
"></xop:Include></ns1:image></ns1:mtomSample>
Recieved Fault : <soapenv:Fault xmlns:soapenv="
http://schemas.xmlsoap.org/soap/e
nvelope/"><faultcode>soapenv:Client</faultcode><faultstring>SOAP message
does no
t contain a SOAP envelope element</faultstring></soapenv:Fault>
-----------------------------------------------------------------------------------------------------------------------------------------

packages we captured:
--------------------------------------------------------------------------------------------------------------------
POST /axis2/services/bss_service_trs HTTP/1.1

User-Agent: Axis2C/1.6.0

SOAPAction: ""

Transfer-Encoding: chunked

Content-Type: multipart/related;
boundary=MIMEBoundary161d2f8a-024f-4977-bb77-1c8b6c8303eb;
type="application/xop+xml"; start="<
0.6d6511ed-2461-414d-b850-bb209dabc5a0@apache.org>"; start-info="text/xml";
charset="UTF-8"

Host: 10.24.2.2:8080



32

--MIMEBoundary161d2f8a-024f-4977-bb77-1c8b6c8303eb

2





a6

content-transfer-encoding: binary

content-id: <0.6d6511ed-2461-414d-b850-bb209dabc5a0@apache.org>

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



2





19b

<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns1:mtomSample
xmlns:ns1="http://ws.apache.org/axis2/c/samples/mtom"><ns1:fileName>test.jpg</ns1:fileName><ns1:image><xop:Include
xmlns:xop="http://www.w3.org/2004/08/xop/include" href="
cid:1.9971c660-0b4d-44d6-89ad-66392b09d352@apache.org<cid%3A1.9971c660-0b4d-44d6-89ad-66392b09d352@apache.org>
"></xop:Include></ns1:image></ns1:mtomSample></soapenv:Body></soapenv:Envelope>



32

--MIMEBoundary161d2f8a-024f-4977-bb77-1c8b6c8303eb

2





80

content-transfer-encoding: binary

content-id: <1.9971c660-0b4d-44d6-89ad-66392b09d352@apache.org>

content-type: image/jpeg





2





34

--MIMEBoundary161d2f8a-024f-4977-bb77-1c8b6c8303eb--

0



HTTP/1.1 500 Internal Server Error

Date: Mon, 30 Mar 2009 08:01:55 GMT

Server: Apache/2.2.3 (Red Hat)

Connection: close

Transfer-Encoding: chunked

Content-Type: multipart/related;
boundary=MIMEBoundary0952b37a-1d01-1de1-3024-001e4fd3ad50;
type="application/xop+xml"; start="<
0.0952b410-1d01-1de1-3025-001e4fd3ad50@apache.org>"; start-info="text/xml";
charset="UTF-8"



243

--MIMEBoundary0952b37a-1d01-1de1-3024-001e4fd3ad50

content-transfer-encoding: binary

content-id: <0.0952b410-1d01-1de1-3025-001e4fd3ad50@apache.org>

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



<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header></soapenv:Header><soapenv:Body><soapenv:Fault><faultcode>soapenv:Client</faultcode><faultstring>SOAP
message does not contain a SOAP envelope
element</faultstring></soapenv:Fault></soapenv:Body></soapenv:Envelope>

--MIMEBoundary0952b37a-1d01-1de1-3024-001e4fd3ad50--

0


2009/3/30 Manjula Peiris <manjula@wso2.com>

> Zhang,
>
> Seems to me your message doesn't have any <xop:Include> elements ? Are
> you creating the data_handlers correctly in your client code ? Please
> see the mtom sample for more information.
>
> Thanks,
> Manjula.
>
>
> On Mon, 2009-03-30 at 14:31 +0800, Yuanfeng Zhang wrote:
> > 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