Would try to set that appropriately in axis2.xml
<!--During a fault, stack trace can be sent with the fault message.
The following flag will control -->
<!--that behavior.-->
<parameter name="sendStacktraceDetailsWithFaults">false</parameter>
<!--If there aren't any information available to find out the fault
reason, we set the message of the exception-->
<!--as the faultreason/Reason. But when a fault is thrown from a
service or some where, it will be -->
<!--wrapped by different levels. Due to this the initial exception
message can be lost. If this flag-->
<!--is set, then Axis2 tries to get the first exception and set its
message as the faultreason/Reason.-->
<parameter
name="DrillDownToRootCauseForFaultReason">false</parameter>
Maybe it helps
Josef
Von: Dan Haywood [mailto:dhayw...@equalexperts.com]
Gesendet: Dienstag, 25. Oktober 2011 13:49
An: java-user@axis.apache.org
Betreff: Re: error handling - please help
wireshark?
On 25 October 2011 10:58, Grant Maxwell <grant.maxw...@maxan.com.au>
wrote:
Hi
Can anyone help with this please ?
suggestion to use tools like tcp monitor will not work. We need to get =
the error information inside the application and handle the error.=20
advice on how to get the original incoming packet containing the error =
information would be much appreciated
regards
Grant
On 21/10/2011, at 7:37 AM, Deepal Jayasinghe wrote:
> TCP Monitor lets you to send the message through it (change the URL
> address of the request) and you can see the outgoing and incoming
message.
>
> In addition please check the stax-impl you are using
> "com.ctc.wstx.exc.WstxUnexpectedCharException"
>
> Deepal
>
> On 10/20/2011 4:09 PM, Grant Maxwell wrote:
>> Thanks for the reply Deepal
>>
>> To be clear - I need to deal with these messages in the =
>> application, not as an external monitor. Otherwise I will never be
able =
>> to rely on the system for processing integrity.=09
>> Catching the exception is just the start. I have to be able to =
>> work out what went wrong (in the program) and getting the original =
>> incoming message is probably the only way to do that.
>>
>> regards
>> Grant
>>
>> On 20/10/2011, at 11:49 PM, Deepal Jayasinghe wrote:
>>
>>> Use TCP monitor [1] and log the outgoing and incoming message.
>>>
>>> [1]: http://ws.apache.org/commons/tcpmon/download.cgi
>>>
>>> Deepal
>>>
>>>> Hi
>>>>
>>>> I am writing a java/axis2 program to access a remote service
written in .Net.
>>>>
>>>> The problem I am having is that when the remote service does not
like our request for some reason it does not return a soap message but
rather outputs an
>>>> http message like:
>>>> Server was unable to process request. ---> ERROR: 22003: integer
out of range
>>>>
>>>> Of course axis2 does spits the dummy with:
>>>>
>>>> org.apache.axis2.AxisFault:
com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'S'
(code 83) in prolog; expected '<'
>>>> at [row,col {unknown-source}]: [1,1]
>>>> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>>>> at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti
ls.java:123)
>>>> at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti
ls.java:67)
>>>> at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(Out
InAxisOperation.java:354)
>>>> at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:421)
>>>> at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA
xisOperation.java:229)
>>>> at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:165
)
>>>> at
com.XXXXXX.api.DistributorStub.insertLocation(DistributorStub.java:1111)
>>>> at
org.opengts.servers.taip.TrackClientPacketHandler.parseInsertRecord_RTCP
(TrackClientPacketHandler.java:693)
>>>> at
org.opengts.servers.taip.TrackClientPacketHandler.parseInsertRecord(Trac
kClientPacketHandler.java:177)
>>>> at
org.opengts.servers.taip.TrackClientPacketHandler.getHandlePacket(TrackC
lientPacketHandler.java:163)
>>>> at
org.opengts.util.ServerSocketThread$ServerSessionThread.run(ServerSocket
Thread.java:1444)
>>>>
>>>>
>>>> I'm quite new to axis2 and am struggling with how to capture this
message and deal with it.
>>>> My first instinct is to get the original text from the failed
message and log the reason, but I cant work out how to retrieve the text
message.
>>>> I was only able to get the message (above) via tcpdump and
wireshark :(
>>>>
>>>> Can anyone please tell me how to access the incoming message text ?
>>>>
>>>> or
>>>>
>>>> how to better handle this exception in such a way as to log the
cause.
>>>>
>>>> regards
>>>> Grant
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
>>>> For additional commands, e-mail: java-user-h...@axis.apache.org
>>>>
>>>>
>>> --
>>> Blog - http://blogs.deepal.org/
>>>
>>>
---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
>>> For additional commands, e-mail: java-user-h...@axis.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
>> For additional commands, e-mail: java-user-h...@axis.apache.org
>>
>>
>
> --
> Blog - http://blogs.deepal.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-user-h...@axis.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org
