wood burning stoves 2.0*
The moose likes Web Services and the fly likes Webservices errors Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Webservices errors" Watch "Webservices errors" New topic
Author

Webservices errors

Chenna Krishna
Ranch Hand

Joined: Dec 13, 2002
Posts: 34
Hi guys,
I am using Axis1_1 and tomcat 4.1.3
new to webservices and when I try to run some samples on my windows getting folling error.

2004/10/16 22:26:29.125 BST WARNING 11 Communication failure for activity 570
2004/10/16 22:26:29.125 BST FINE 11 Communication failure for activity 570: java.lang.ClassCastException
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.ClassCastException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace: AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.ClassCastException
faultActor:
faultNode:
faultDetail:

java.lang.ClassCastException
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:260)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:169)
at org.apache.axis.encoding.DeserializationContextImpl.endElement(DeserializationContextImpl.java:1015)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1712)
at org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
at org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:242)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:538)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:376)
at org.apache.axis.client.Call.invokeEngine(Call.java:2583)
at org.apache.axis.client.Call.invoke(Call.java:2553)
at org.apache.axis.client.Call.invoke(Call.java:2248)
at org.apache.axis.client.Call.invoke(Call.java:2171)
at org.apache.axis.client.Call.invoke(Call.java:1691)
at com.alcatel.commonprovisioning.client.VoIPUserManagementSoapBindingStub.createVoIPUser(VoIPUserManagementSoapBindingStub.java:241)
at com.bt.clickdial.tactoss.ScpConfigurationService.configure(ScpConfigurationService.java:158)
at com.bt.clickdial.tactoss.ScpConfigurationService.run(ScpConfigurationService.java:97)
at java.lang.Thread.run(Thread.java:534)

-----------------------------

Can some one help on this?

Thanks & Regards,

Chenna
Pradeep Ram
Greenhorn

Joined: Sep 29, 2004
Posts: 18
If you are using Axis, try to use TCPMon (TCP Monitoring tool) to look at the SOAP messages that were formed at your end. This would help you diagnose message related errors.

Its a little difficult to diagnose the problem from the error message, it appears that there is some kind of casting problem. Unfortunately the faultActor attribute is empty, so we have no clue as to who caused the problem. Try to run a debug tool against your application to see where the request fails.

Are you using handlers and chains for this application ?

--Pradeep
 
 
subject: Webservices errors