You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Vikram Chiruvolu <vi...@yahoo.com> on 2001/08/04 08:07:58 UTC
strange problem
With SOAP 2.2, Xerces 1.3.1, Tomcat 3.23, Apache 1.3,
and NTS 4 ... I've worked through all the issues &
have my server responding properly from the browser,
that it only reponds to POST requests. Now when I try
to test my client install on the server itself by
executing locally:
java org.apache.soap.server.ServiceManagerClient
http://localhost:8080/soap/servlet/messagerouter list
where CLASSPATH =
E:\soap-bin-2.2\soap-2_2\lib\soap.jar;E:\Xerces\xerces-1_3_1\xerces.jar;E:\javamail\javamail-1.2\mail.jar;E:\jaf-1.0.1\activation.jar;E:\bsf-2_2\lib\bsf.jar;E:\rhino\js.jar
org.apache.soap.server.ServiceManagerClient list
..... and I get this strange error, not mentioned in
the Troubleshooting guide.......
Exception in thread "main" [SOAPException:
faultCode=SOAP-ENV:Client; msg=A
'http://schemas.xmlsoap.org/soap/envelope/:Fault'
element must contain a: 'faultcode' element.;
targetException=java.lang.IllegalArgumentException: A
'http://schemas.xmlsoap.org/soap/envelope/:Fault'
element must contain a: 'faultcode' element.]
at
org.apache.soap.rpc.Call.invoke(Call.java:246)
at
org.apache.soap.server.ServiceManagerClient.invokeMethod(ServiceManagerClient.java:129)
at
org.apache.soap.server.ServiceManagerClient.list(ServiceManagerCl
ient.java:151)
at
org.apache.soap.server.ServiceManagerClient.main(ServiceManagerCl
ient.java:237)
Looks like an SOAP document is being validated against
the schema, and failing because the <Faultcode>
element does not have a <fault> element within it...
I'm running the soap.jar file dated 5/29/01.
Anyone else experienced this? Am I doing something
wrong or is this a bug to cross-list to the dev group?
Thanks,
Vikram
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
Re: strange problem
Posted by William Brogden <wb...@bga.com>.
Vikram Chiruvolu wrote:
>
> With SOAP 2.2, Xerces 1.3.1, Tomcat 3.23, Apache 1.3,
> and NTS 4 ... I've worked through all the issues &
> have my server responding properly from the browser,
> that it only reponds to POST requests. Now when I try
> to test my client install on the server itself by
> executing locally:
>
> java org.apache.soap.server.ServiceManagerClient
> http://localhost:8080/soap/servlet/messagerouter list
>
> where CLASSPATH =
> E:\soap-bin-2.2\soap-2_2\lib\soap.jar;E:\Xerces\xerces-1_3_1\xerces.jar;E:\javamail\javamail-1.2\mail.jar;E:\jaf-1.0.1\activation.jar;E:\bsf-2_2\lib\bsf.jar;E:\rhino\js.jar
> org.apache.soap.server.ServiceManagerClient list
>
> ..... and I get this strange error, not mentioned in
> the Troubleshooting guide.......
>
> Exception in thread "main" [SOAPException:
> faultCode=SOAP-ENV:Client; msg=A
> 'http://schemas.xmlsoap.org/soap/envelope/:Fault'
> element must contain a: 'faultcode' element.;
> targetException=java.lang.IllegalArgumentException: A
> 'http://schemas.xmlsoap.org/soap/envelope/:Fault'
> element must contain a: 'faultcode' element.]
> at
> org.apache.soap.rpc.Call.invoke(Call.java:246)
> at
That is an error message from the client which is concealing
the real problem - for some reason the server is sending back
a plain HTML error message. Probably your request did not
go all the way through to messagerouter.
Use the tcptunnel or similar utility that lets you
see the exact text of the request and response.
I have written a utility "UtilSnoop" that will do this - see:
http://www.lanw.com/books/javasoap/default.htm
--
WBB - wbrogden@lanw.com
Java Cert mock exams http://www.lanw.com/java/javacert/
Author of Java Developer's Guide to Servlets and JSP
ISBN 0-7821-2809-2
Re: strange problem
Posted by William Brogden <wb...@bga.com>.
Vikram Chiruvolu wrote:
>
> With SOAP 2.2, Xerces 1.3.1, Tomcat 3.23, Apache 1.3,
> and NTS 4 ... I've worked through all the issues &
> have my server responding properly from the browser,
> that it only reponds to POST requests. Now when I try
> to test my client install on the server itself by
> executing locally:
>
> java org.apache.soap.server.ServiceManagerClient
> http://localhost:8080/soap/servlet/messagerouter list
>
> where CLASSPATH =
> E:\soap-bin-2.2\soap-2_2\lib\soap.jar;E:\Xerces\xerces-1_3_1\xerces.jar;E:\javamail\javamail-1.2\mail.jar;E:\jaf-1.0.1\activation.jar;E:\bsf-2_2\lib\bsf.jar;E:\rhino\js.jar
> org.apache.soap.server.ServiceManagerClient list
>
> ..... and I get this strange error, not mentioned in
> the Troubleshooting guide.......
>
> Exception in thread "main" [SOAPException:
> faultCode=SOAP-ENV:Client; msg=A
> 'http://schemas.xmlsoap.org/soap/envelope/:Fault'
> element must contain a: 'faultcode' element.;
> targetException=java.lang.IllegalArgumentException: A
> 'http://schemas.xmlsoap.org/soap/envelope/:Fault'
> element must contain a: 'faultcode' element.]
> at
> org.apache.soap.rpc.Call.invoke(Call.java:246)
> at
That is an error message from the client which is concealing
the real problem - for some reason the server is sending back
a plain HTML error message. Probably your request did not
go all the way through to messagerouter.
Use the tcptunnel or similar utility that lets you
see the exact text of the request and response.
I have written a utility "UtilSnoop" that will do this - see:
http://www.lanw.com/books/javasoap/default.htm
--
WBB - wbrogden@lanw.com
Java Cert mock exams http://www.lanw.com/java/javacert/
Author of Java Developer's Guide to Servlets and JSP
ISBN 0-7821-2809-2
RE: strange problem
Posted by Vikram Chiruvolu <vi...@yahoo.com>.
Tom -
Thank you -- I hadn't checked that FAQ yet tho I should've!
It's also the first listing on Google when you put in this error ....
Will try to be more resourceful before I post next time ...
Thx,
V
-----Original Message-----
From: Tom Myers [mailto:tommyers@dreamscape.com]
Sent: Sunday, August 05, 2001 10:16 AM
To: soap-user@xml.apache.org
Cc: soap-user@xml.apache.org
Subject: Re: strange problem
At 11:07 PM 8/3/2001 -0700, Vikram Chiruvolu wrote:
>With SOAP 2.2, Xerces 1.3.1, Tomcat 3.23, Apache 1.3,
...
>..... and I get this strange error, not mentioned in
>the Troubleshooting guide.......
>
>Exception in thread "main" [SOAPException:
>faultCode=SOAP-ENV:Client; msg=A
>'http://schemas.xmlsoap.org/soap/envelope/:Fault'
>element must contain a: 'faultcode' element.;
http://xml.apache.org/soap/faq/faq_chawke.html#Q1_1
:-)
Tom Myers
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
RE: strange problem
Posted by Vikram Chiruvolu <vi...@yahoo.com>.
Tom -
Thank you -- I hadn't checked that FAQ yet tho I should've!
It's also the first listing on Google when you put in this error ....
Will try to be more resourceful before I post next time ...
Thx,
V
-----Original Message-----
From: Tom Myers [mailto:tommyers@dreamscape.com]
Sent: Sunday, August 05, 2001 10:16 AM
To: soap-user@xml.apache.org
Cc: soap-user@xml.apache.org
Subject: Re: strange problem
At 11:07 PM 8/3/2001 -0700, Vikram Chiruvolu wrote:
>With SOAP 2.2, Xerces 1.3.1, Tomcat 3.23, Apache 1.3,
...
>..... and I get this strange error, not mentioned in
>the Troubleshooting guide.......
>
>Exception in thread "main" [SOAPException:
>faultCode=SOAP-ENV:Client; msg=A
>'http://schemas.xmlsoap.org/soap/envelope/:Fault'
>element must contain a: 'faultcode' element.;
http://xml.apache.org/soap/faq/faq_chawke.html#Q1_1
:-)
Tom Myers
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Re: strange problem
Posted by Tom Myers <to...@dreamscape.com>.
At 11:07 PM 8/3/2001 -0700, Vikram Chiruvolu wrote:
>With SOAP 2.2, Xerces 1.3.1, Tomcat 3.23, Apache 1.3,
...
>..... and I get this strange error, not mentioned in
>the Troubleshooting guide.......
>
>Exception in thread "main" [SOAPException:
>faultCode=SOAP-ENV:Client; msg=A
>'http://schemas.xmlsoap.org/soap/envelope/:Fault'
>element must contain a: 'faultcode' element.;
http://xml.apache.org/soap/faq/faq_chawke.html#Q1_1
:-)
Tom Myers
Re: strange problem
Posted by Gordon Easton <go...@yahoo.com>.
It might be that you are sending the request to the wrong place.
Try sending your "list" request to:
http://localhost:8080/soap/servlet/rpcrouter
--- Vikram Chiruvolu <vi...@yahoo.com> wrote:
> With SOAP 2.2, Xerces 1.3.1, Tomcat 3.23, Apache 1.3,
> and NTS 4 ... I've worked through all the issues &
> have my server responding properly from the browser,
> that it only reponds to POST requests. Now when I try
> to test my client install on the server itself by
> executing locally:
>
> java org.apache.soap.server.ServiceManagerClient
> http://localhost:8080/soap/servlet/messagerouter list
>
>
> where CLASSPATH =
>
E:\soap-bin-2.2\soap-2_2\lib\soap.jar;E:\Xerces\xerces-1_3_1\xerces.jar;E:\javamail\javamail-1.2\mail.jar;E:\jaf-1.0.1\activation.jar;E:\bsf-2_2\lib\bsf.jar;E:\rhino\js.jar
> org.apache.soap.server.ServiceManagerClient list
>
> ..... and I get this strange error, not mentioned in
> the Troubleshooting guide.......
>
> Exception in thread "main" [SOAPException:
> faultCode=SOAP-ENV:Client; msg=A
> 'http://schemas.xmlsoap.org/soap/envelope/:Fault'
> element must contain a: 'faultcode' element.;
> targetException=java.lang.IllegalArgumentException: A
> 'http://schemas.xmlsoap.org/soap/envelope/:Fault'
> element must contain a: 'faultcode' element.]
> at
> org.apache.soap.rpc.Call.invoke(Call.java:246)
> at
>
org.apache.soap.server.ServiceManagerClient.invokeMethod(ServiceManagerClient.java:129)
> at
> org.apache.soap.server.ServiceManagerClient.list(ServiceManagerCl
> ient.java:151)
> at
> org.apache.soap.server.ServiceManagerClient.main(ServiceManagerCl
> ient.java:237)
>
> Looks like an SOAP document is being validated against
> the schema, and failing because the <Faultcode>
> element does not have a <fault> element within it...
> I'm running the soap.jar file dated 5/29/01.
>
> Anyone else experienced this? Am I doing something
> wrong or is this a bug to cross-list to the dev group?
>
> Thanks,
> Vikram
>
>
> __________________________________________________
> Do You Yahoo!?
> Make international calls for as low as $.04/minute with Yahoo!
> Messenger
> http://phonecard.yahoo.com/
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
Re: strange problem
Posted by Gordon Easton <go...@yahoo.com>.
It might be that you are sending the request to the wrong place.
Try sending your "list" request to:
http://localhost:8080/soap/servlet/rpcrouter
--- Vikram Chiruvolu <vi...@yahoo.com> wrote:
> With SOAP 2.2, Xerces 1.3.1, Tomcat 3.23, Apache 1.3,
> and NTS 4 ... I've worked through all the issues &
> have my server responding properly from the browser,
> that it only reponds to POST requests. Now when I try
> to test my client install on the server itself by
> executing locally:
>
> java org.apache.soap.server.ServiceManagerClient
> http://localhost:8080/soap/servlet/messagerouter list
>
>
> where CLASSPATH =
>
E:\soap-bin-2.2\soap-2_2\lib\soap.jar;E:\Xerces\xerces-1_3_1\xerces.jar;E:\javamail\javamail-1.2\mail.jar;E:\jaf-1.0.1\activation.jar;E:\bsf-2_2\lib\bsf.jar;E:\rhino\js.jar
> org.apache.soap.server.ServiceManagerClient list
>
> ..... and I get this strange error, not mentioned in
> the Troubleshooting guide.......
>
> Exception in thread "main" [SOAPException:
> faultCode=SOAP-ENV:Client; msg=A
> 'http://schemas.xmlsoap.org/soap/envelope/:Fault'
> element must contain a: 'faultcode' element.;
> targetException=java.lang.IllegalArgumentException: A
> 'http://schemas.xmlsoap.org/soap/envelope/:Fault'
> element must contain a: 'faultcode' element.]
> at
> org.apache.soap.rpc.Call.invoke(Call.java:246)
> at
>
org.apache.soap.server.ServiceManagerClient.invokeMethod(ServiceManagerClient.java:129)
> at
> org.apache.soap.server.ServiceManagerClient.list(ServiceManagerCl
> ient.java:151)
> at
> org.apache.soap.server.ServiceManagerClient.main(ServiceManagerCl
> ient.java:237)
>
> Looks like an SOAP document is being validated against
> the schema, and failing because the <Faultcode>
> element does not have a <fault> element within it...
> I'm running the soap.jar file dated 5/29/01.
>
> Anyone else experienced this? Am I doing something
> wrong or is this a bug to cross-list to the dev group?
>
> Thanks,
> Vikram
>
>
> __________________________________________________
> Do You Yahoo!?
> Make international calls for as low as $.04/minute with Yahoo!
> Messenger
> http://phonecard.yahoo.com/
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
Re: strange problem
Posted by Tom Myers <to...@dreamscape.com>.
At 11:07 PM 8/3/2001 -0700, Vikram Chiruvolu wrote:
>With SOAP 2.2, Xerces 1.3.1, Tomcat 3.23, Apache 1.3,
...
>..... and I get this strange error, not mentioned in
>the Troubleshooting guide.......
>
>Exception in thread "main" [SOAPException:
>faultCode=SOAP-ENV:Client; msg=A
>'http://schemas.xmlsoap.org/soap/envelope/:Fault'
>element must contain a: 'faultcode' element.;
http://xml.apache.org/soap/faq/faq_chawke.html#Q1_1
:-)
Tom Myers