Menu
▾
▴
RE: [ebxmlms-develop] SOAPException: Unable to internalize messag e (Invalid Content-Typ e:text/html)
|
From: Ronald v. K. <rv...@ab...> - 2003-03-20 10:17:34
|
FYI
Bea, at least up to weblogic 6.1sp3 has the same problem. We therefor used
the sun activation.jar in front of the weblogic.jar. I did not try this with
hermes yet, but multipart-mime generally has this problem in Bea
Ronald
-----Oorspronkelijk bericht-----
Van: Patrick Yee [mailto:kc...@ce...]
Verzonden: donderdag 20 maart 2003 10:54
Aan: ebx...@li...
Onderwerp: Re: [ebxmlms-develop] SOAPException: Unable to internalize messag
e (Invalid Content-Typ e:text/html)
Peter,
Thank you for your note.
Please check out the latest CVS source tree and try again. We have committed
the change to make the Content-Type not wrapped. What a coincident! We have
made the change to get Hermes deployable in Websphere.
Regards, -Patrick
----- Original Message -----
From: Mayne, Peter <mailto:Pet...@ap...>
To: 'ebx...@li...'
<mailto:'ebx...@li...'>
Sent: Thursday, March 20, 2003 6:13 AM
Subject: RE: [ebxmlms-develop] SOAPException: Unable to internalize messag e
(Invalid Content-Typ e:text/html)
This turns out to be a bug in Apache. If the header is wrapped (as the
Content-Type header is) and it is a multiple of eight bytes long when
unwrapped (which this one is), then not enough space is allocated for the
header value, and the next header overwrites the end of this value.
Therefore, the Content-Type header breaks, which breaks the parsing of the
SOAP message. However, instead of an obvious error (like "could not find
boundary"), SAAJ throws something about text/html, which doesn't appear
anywhere.
There's one problem fixed, anyway.
PJDM
--
Peter Mayne
Technology Consultant
Spherion Technology Solutions
Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602
T: 61 2 62689727 F: 61 2 62689777
-----Original Message-----
From: Mayne, Peter
Sent: Wednesday, 19 March 2003 4:36 PM
To: 'ebx...@li...'
Subject: RE: [ebxmlms-develop] SOAPException: Unable to internalize messag e
(Invalid Content-Typ e:text/html)
That doesn't seem to be the problem, but it nudged me into looking in the
right place.
I'm using Apache (to provide SSL + user authentication) in front of Tomcat,
connected with the JK2 connector. I've inserted some debugging printlns in
MessageServicehandler to figure out what's going on.
If I send the incoming message directly to Tomcat, everything works fine. In
particular, the content type is:
multipart/related; type="text/xml";
boundary="----=_Part_9_24374438.1048047839137"
If I send the incoming message to Tomcat via Apache, the content-type is:
multipart/related; type="text/xml";
boundary="----=_Part_9_24374438.1048047839137"SOAPAction
which is obviously incorrect, and which therefore causes
soapMessage = messageFactory.createMessage
(headers, new ByteArrayInputStream(requestBytes));
because the headers are broken. (If I insert some more code just before this
to take the extra text out of the header, everything works fine.)
Wild guess: the bug would appear to be in the JK2 area. More debugging
coming up...
Incidentally, I was seeing this problem a long time before I started using
JK2. I have no idea what was doing it then.
PJDM
--
Peter Mayne
Technology Consultant
Spherion Technology Solutions
Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602
T: 61 2 62689727 F: 61 2 62689777
> -----Original Message-----
> From: Ng Chi Yuen [Cyng] [ mailto:cy...@cs...
<mailto:cy...@cs...> ]
> Sent: Wednesday, 19 March 2003 2:40 PM
> To: Ebxmlms Developers List
> Subject: Re: [ebxmlms-develop] SOAPException: Unable to
> internalize message (Invalid Content-Typ e:text/html)
>
>
> Hi,
>
> > java.security.PrivilegedActionException:
> javax.xml.soap.SOAPException:
> > Unable to internalize message
> >
> > with the accompanying exceptions. I have no idea what
> causes it: they'll
> > just start happening. I have no diea how to stop it either;
> eventually
> > things will go back to normal.
> >
> > Would anybody care to hazard a guess as to what's going on?
> >
> > javax.xml.soap.SOAPException: Invalid Content-Type:text/html
> ^^^^^^^^^
>
> It seems that your receiver answers HTTP_OK (200) with
> Content-Type being text/html. When JAXM sends a SOAPMessage out, it
> expects a text/xml response for HTTP_OK when unmarshalling
> the response
> message. Otherwise, SOAPException will be thrown by JAXM.
>
> Regards,
> CY
>
> --------------------------------------------------------------
> --------------
> Ng Chi Yuen, CY. cy...@ce...
> http://www.cecid.hku.hk/ <http://www.cecid.hku.hk/>
> Technology Officer,
> Centre for
> E-Commerce Infrastructure Development,
> The University of Hong Kong
> --------------------------------------------------------------
> --------------
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink?
> You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
<http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en>
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
<https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop>
>
The information contained in this email and any attachments to it:
(a) may be confidential and if you are not the intended recipient, any
interference with,
use, disclosure or copying of this material is unauthorised and prohibited;
and
(b) may contain personal information of the recipient and/or the sender as
defined
under the Privacy Act 1988 (Cth). Consent is hereby given by the
recipient(s) to
collect, hold and use such information and any personal information
contained in a
response to this email, for any reasonable purpose in the ordinary course of
Spherion's
business, including forwarding this email internally or disclosing it to a
third party. All
personal information collected by Spherion will be handled in accordance
with
Spherion's Privacy Policy. If you have received this email in error, please
notify the
sender and delete it.
(c) you agree not to employ or arrange employment for any candidate(s)
supplied in
this email and any attachments without first entering into a contractual
agreement with
Spherion. You further agree not to divulge any information contained in this
document
to any person(s) or entities without the express permission of Spherion.
|
