Menu
▾
▴
RE: [ebxmlms-general] Digital signature
|
From: Larchier C. <cla...@ax...> - 2003-11-17 10:15:07
|
Patrick,
=20
The answer is yes for your 2 first questions.
=20
I have uncommented the following lines in msh.properties.xml (and =
restarted Tomcat) :
<Proxy>
<Host>localhost</Host>
<Port>8282</Port>
</Proxy>
But it seems changing nothing.
In the msh.log trace I always have :
2003-11-17 10:00:49,687 INFO [Thread-18]: Sending message to =
http://localhost:8080/msh
And with TCPMon I get nothing on 8282 port.
=20
Is there something else to do?
=20
Christophe
-----Message d'origine-----
De : ebx...@li... =
[mailto:ebx...@li...]De la part de =
Patrick Yee
Envoy=E9 : samedi 15 novembre 2003 15:19
=C0 : ebx...@li...
Objet : Re: [ebxmlms-general] Digital signature
Christophe,
=20
So you have send out the message twice using Monitor, once without using =
digital signature, once with digital signature, right? Are you using =
exactly the same parameters in Monitor, with only the digital signature =
check box in the latter case?
=20
If the answer is yes, we have still no clue about what's happening in =
your case. To further investigate, you can try to grab a very useful =
tool called TCPMon from Apache AXIS project. This tool should be =
installed between your Monitor and the MSH server, and it can help you =
to capture all the HTTP level traffic between Monitor and MSH server, =
and then forward the captured traffic out as a proxy.=20
=20
It will be useful to capture the text/plain message to see the cause.
=20
Regards, -Patrick
=20
----- Original Message -----=20
From: Larchier <mailto:cla...@ax...> Christophe=20
To: ebx...@li...=20
Sent: Friday, November 14, 2003 3:31 PM
Subject: RE: [ebxmlms-general] Digital signature
It's a loopback test.
Note that the loopback test without digital signature works fine.
=20
Christophe
-----Message d'origine-----
De : ebx...@li... =
[mailto:ebx...@li...]De la part de =
Patrick Yee
Envoy=E9 : jeudi 13 novembre 2003 11:32
=C0 : ebx...@li...
Objet : Re: [ebxmlms-general] Digital signature
Larchier,
Where did you send the message to? It seems that the target end sent =
back a message that is not comprehensible by Hermes.
Regards, -Patrick
Larchier Christophe wrote:
Hi all,=20
With the MSH monitor, when I send a message with digital signature, I =
get the following message in the Tomcat console :=20
javax.xml.soap.SOAPException: Invalid Content-Type:text/plain=20
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159) =
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)=20
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon=
nection.java:333)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.=
run(HttpSOAPConnection.java:142)=20
at java.security.AccessController.doPrivileged(Native Method)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon=
nection.java:115)=20
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20
at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown =
Source)=20
javax.xml.soap.SOAPException: Unable to internalize message=20
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135) =
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon=
nection.java:333)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.=
run(HttpSOAPConnection.java:142)=20
at java.security.AccessController.doPrivileged(Native Method)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon=
nection.java:115)=20
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20
at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown =
Source)=20
Caused by: javax.xml.soap.SOAPException: Invalid Content-Type:text/plain =
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159) =
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)=20
... 7 more=20
java.security.PrivilegedActionException: javax.xml.soap.SOAPException: =
Unable to internalize message=20
at java.security.AccessController.doPrivileged(Native Method)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon=
nection.java:115)=20
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20
at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown =
Source)=20
Caused by: javax.xml.soap.SOAPException: Unable to internalize message=20
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135) =
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon=
nection.java:333)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.=
run(HttpSOAPConnection.java:142)=20
... 4 more=20
After few minutes, I receive an error message : "Delivery failure".=20
Thanks for your help.=20
______________________________________=20
Christophe Larchier=20
Axway.=20
a Sopra Group company.=20
3, rue de Pr=E9 Faucon=20
PAE - Les Glaisins - BP238=20
F-74942 Annecy-le-Vieux Cedex=20
* +33 (0)4 50 33 31 55=20
______________________________________=20
------------------------------------------------------- This SF.Net =
email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn =
firsthand the latest developments in Apache, PHP, Perl, XML, Java, =
MySQL, WebDAV, and more! http://www.apachecon.com/ =
_______________________________________________ ebxmlms-general mailing =
list ebx...@li... =
https://lists.sourceforge.net/lists/listinfo/ebxmlms-general=20
|
