• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Issue while invoking Web Services with Axis....

 
vara prakash
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

I am using axis 1.0 to invoke a web service deployed on web logic server 8.1. I have generated the client side Java Classes and Stubs using WSDL2Java tool of axis. When I try to invoke the remote method, I was getting the following exception. I am not always getting this exception. Sometimes I could hit the remote service with the same data.

Could some one help me resolve this issue and let me know what could be the reason. I really don't understand why is it working some times and why not some times....

AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
faultString: Exception during processing: java.lang.NullPointerException (see Fault Detail for stacktrace)
faultActor: null
faultDetail:
stacktrace: null

Exception during processing: java.lang.NullPointerException (see Fault Detail for stacktrace)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:135)
at org.apache.axis.encoding.DeserializationContextImpl.endElement(DeserializationContextImpl.java:904)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:213)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:457)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:362)
at org.apache.axis.client.Call.invokeEngine(Call.java:2046)
at org.apache.axis.client.Call.invoke(Call.java:2016)
at org.apache.axis.client.Call.invoke(Call.java:1786)
at org.apache.axis.client.Call.invoke(Call.java:1711)
at org.apache.axis.client.Call.invoke(Call.java:1251)
at ict.external.euam.TestPortBindingStub.addPlan(TestPortBindingStub.java:285)


Thanks in advance.
Vara Prakash
 
Harish Madhavan
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Doubt if right jar is loaded from the weblogic end.Some mismatch in the deserializers implementation.Can you confirm :
> If you are having your own axis.jar under WEB-INF/lib ?
> Check weblogic documentation if it has inbuilt axis api's.I know websphere 5.x has,but not sure on weblogic.

Harish
 
Tim West
Ranch Hand
Posts: 539
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Weblogic does not use Axis in any way.

I know this isn't the most useful advice, but can you upgrade to Axis 1.2? 1.0 is very old now, and the issue you're hitting (which looks rather like a bug) may have been resolved.

Finally, my natural tendency is to put the fault on the Axis side - Weblogic 8.1 is the best WS platform I've tried yet. (Note that the fact that the exception was thrown on the Axis side does not mean that the problem originates there. Weblogic could be returning an invalid SOAP message, in which case Axis may fail unexpectedly.)


-Tim
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic