[ebxmlms-general] problem message: hermes throws exception on echo.

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Ron,

    Here is the echo message that caused the problem (between echo lines)!

----------echo-------------------------

------=_Part_2_24749215.1068222593281
Content-Type: text/xml
Content-Id: <soappart>

<?xml version="1.0" encoding="UTF-8"?>
<soap-env:Envelope xmlns:soap-env="
http://schemas.xmlsoap.org/soap/envelope/
<http://schemas.xmlsoap.org/soap/envelope/> " xm
lns:xsi=" http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance> " xmlns:xlink=" http://www.w3.o
<http://www.w3.o> 
rg/1999/xlink" xsi:schemaLocation="
http://schemas.xmlsoap.org/soap/envelope/
<http://schemas.xmlsoap.org/soap/envelope/>  htt
p://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd"><soap-env:H
eade
r xsi:schemaLocation="
http://www.oasis-open.org/committees/ebxml-msg/schema/msg
<http://www.oasis-open.org/committees/ebxml-msg/schema/msg> -
header-2_0.xsd
http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header
<http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header> -
2_0.xsd"><eb:MessageHeader xmlns:eb="
http://www.oasis-open.org/committees/ebxml
<http://www.oasis-open.org/committees/ebxml> -
msg/schema/msg-header-2_0.xsd" eb:version="2.0"
soap-env:mustUnderstand="1"><eb:
From><eb:PartyId
eb:type="fromPartyId">Sample</eb:PartyId></eb:From><eb:To><eb:P
artyId
eb:type="toPartyId">Sampola</eb:PartyId></eb:To><eb:CPAId>CPA_2003</eb:CP
AId><eb:ConversationId>Item_No_128</eb:ConversationId><eb:Service>http://loc
alho
st:9090/loopback</eb:Service><eb:Action>Order</eb:Action><eb:MessageData><eb
:Mes
sageId>20031107-162721578-CPA_2003.http://localhost:9090/loopback.Order.1@10
.24.
200.237</eb:MessageId><eb:Timestamp>2003-11-07T16:27:21Z</eb:Timestamp></eb:
Mess
ageData></eb:MessageHeader></soap-env:Header><soap-env:Body
xsi:schemaLocation="
http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd
<http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd>
http://
 <http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd>
www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><eb:Manif
est
xmlns:eb="
http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.x
<http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.x> 
sd" eb:version="2.0"><eb:Reference eb:id="contentId" xlink:type="simple"
xlink:h
ref="cid:contentId"><eb:Description
xml:lang="en-US">description</eb:Description
></eb:Reference></eb:Manifest></soap-env:Body></soap-env:Envelope>
------=_Part_2_24749215.1068222593281
Content-Type: text/xml
Content-Transfer-Encoding: binary
Content-Id: <contentId>

<po/>

------=_Part_2_24749215.1068222593281--

----------echo-------------------------

regards,
Ajit

-----Original Message-----
From: Ronald van Kuijk [mailto:rv...@ab...]
Sent: Friday, November 07, 2003 9:33 PM
To: 'ebx...@li...'
Subject: RE: [ebxmlms-general] interesting hermes error

Do you get this message in hermes on receiving 'echo'?

This is caused by the servelet not detecting a multipart-mime header. Either
because it's not there or because the format is wrong. There has been
problems with the mail/activation libraries in Bea where they wew unable to
detect a boundary that spanned multiple lines. (spanning is done by having
the second line begin with a whitespace character, which bea failed to
detect). An plain html or a simple xml (including a echo of an ebxml
envelop!!) response also does not have the boundary set, and therefor leads
to the same error 

Ronald

-----Oorspronkelijk bericht-----
Van: Tripathi, Ajit (GXS) [mailto:Aji...@gx...]
Verzonden: vrijdag 7 november 2003 16:38
Aan: 'ebx...@li...'
Onderwerp: [ebxmlms-general] interesting hermes error

Hi,

    I am using hermes to send a message from hermes to a JAXM servlet. If I
return the same ebXML message in reponse, this is what I am getting.

regards,
Ajit

javax.mail.MessagingException: Missing start boundary
        at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284)
        at
javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172)

        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
18)
        at
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess
ageFactoryImpl.java:32)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:333)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:142)
        at java.security.AccessController.doPrivileged(Native Method)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:115)
        at
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j
ava:231)
        at
hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1
38)
javax.xml.soap.SOAPException: Unable to internalize message
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
35)
        at
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess
ageFactoryImpl.java:32)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:333)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:142)
        at java.security.AccessController.doPrivileged(Native Method)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:115)
        at
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j
ava:231)
        at
hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1
38)
Caused by: javax.mail.MessagingException: Missing start boundary
        at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284)
        at
javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172)

        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
18)