Axis2 / Java automatically generated web stubs

[gwoodhouse]

Hello,

I'm working with Apache Axis2 web stubs and the code that i have
infront of me is a nightmare (ie, its automatically generated with
wsdl2java). It wouldn't be so bad as the code that's been outsourced
wraps it quite nicely.

Unfortunately theres a bug in it right now where and exception is
being thrown on the OperationClient.execute() method whos inner
working aren't visible.

This is the stack trace:
org.apache.axis2.AxisFault: System error.
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:
435)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:
371)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:
417)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:
229)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:
165)

From this, (and google searches) it makes me think the return "System
error" is coming from the webservice i'm calling.

Does anyone have any experience in whats going on here or have any
suggestions as to where to proceede from here?

I'm going to capture the envolope being submitted and recreate it in
SOAPui and see if i get a similar error.

Thanks for any advice!

Graeme

 

[Tom Anderson]

This is the stack trace:
org.apache.axis2.AxisFault: System error.
at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java: 435)

From this, (and google searches) it makes me think the return "System
error" is coming from the webservice i'm calling.

That's what it sounds like to me.

Does anyone have any experience in whats going on here or have any
suggestions as to where to proceede from here?

Use Metro instead!

Okay, serious answer: get a wire dump, or something close to it. You need
to see exactly what's coming over the network to you. Axis2 should really
be passing on any information it has to you, but there's no substitute for
seeing the fault text with your own eyes.

One way to do this is with a tool like Wireshark which works at the
network level. Once you get it going, that's a great tool.

A simpler option would be to enable some logging. I'm not really an Axis2
man, but my understanding is that it uses HttpClient under the hood. That
means you can switch on wire logging in that - you primarily want the
content log, but you might as well switch on header logging too:

http://hc.apache.org/httpclient-3.x/logging.html

Hopefully, once you see the fault text, the problem should be obvious. If
it isn't, you at least have something to talk to the web service provider
about.

I'm going to capture the envolope being submitted and recreate it in
SOAPui and see if i get a similar error.

Also a good idea.

tom

 

[Arne Vajhøj]

I'm working with Apache Axis2 web stubs and the code that i have
infront of me is a nightmare (ie, its automatically generated with
wsdl2java). It wouldn't be so bad as the code that's been outsourced
wraps it quite nicely.

Unfortunately theres a bug in it right now where and exception is
being thrown on the OperationClient.execute() method whos inner
working aren't visible.

This is the stack trace:
org.apache.axis2.AxisFault: System error.
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:
435)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:
371)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:
417)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:
229)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:
165)

From this, (and google searches) it makes me think the return "System
error" is coming from the webservice i'm calling.

Does anyone have any experience in whats going on here or have any
suggestions as to where to proceede from here?

I'm going to capture the envolope being submitted and recreate it in
SOAPui and see if i get a similar error.

AxisFault is just the clients way of handling an exception
from the server.

So I think you should troubleshoot at the server instead
of at the client.

Arne