Re: [ebxmlms-general] Error when using Tomcat 5.x with Hermes 0.9.3.1

[David RR W. <da...@dr...>]

Fabrice,

I have also seen this problem when using Cyclone Commerce with
Hermes.  The Hermes to Cyclone works fine - but the reverse -
Cyclone sending to Hermes - also ends with the Error 302 - address
temporarily moved.

I did not guess this was related to Tomcat - but seems like that may
be the common problem here.  Perhaps a trace of the actual exchange
can show what is being sent differently here to resolve the issue.

Thanks, DW

----- Original Message ----- 
From: "Morin Fabrice" <fm...@ax...>
To: <ebx...@li...>
Sent: Tuesday, December 14, 2004 7:45 AM
Subject: [ebxmlms-general] Error when using Tomcat 5.x with Hermes 0.9.3.1


Hi all,

I can successfully use Hermes 0.9.3.1 with Tomcat 4.1.x (send/receive
messages using 2 monitors on 2 machines works perfectly).

But I have a problem when I replace Tomcat 4.1.x with Tomcat 5.0.30 or
Tomcat 5.5.4. An error happens when I send a message to another Hermes which
use the same Tomcat version (both sides use monitor). This error happen on
the sender side (in the catalina.out file) :

javax.xml.soap.SOAPException: Invalid Content-Type:text/html
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159)
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)
        at
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageFact
oryImpl.java:32)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnec
tion.java:333)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run
(HttpSOAPConnection.java:142)
        at java.security.AccessController.doPrivileged(Native Method)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnec
tion.java:115)
        at hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown
Source)
        at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown
Source)
javax.xml.soap.SOAPException: Unable to internalize message
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135)
        at
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageFact
oryImpl.java:32)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnec
tion.java:333)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run
(HttpSOAPConnection.java:142)
        at java.security.AccessController.doPrivileged(Native Method)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnec
tion.java:115)
        at hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown
Source)
        at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown
Source)

Comparing the Tomcat responses when using Tomcat 4.1.x and Tomcat 5.x (on
receiver side), it appears that Tomcat 4.1.x ends communication with HTTP
204 code (no content), and Tomcat 5.x ends communication with HTTP 302 code
(Moved temporarily).

Any idea ?


Regards,

Fabrice.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
ebxmlms-general mailing list
ebx...@li...
https://lists.sourceforge.net/lists/listinfo/ebxmlms-general