Re: Uncaught Exception Traces - how to get Axis to tell me what they are

2005-10-03 Thread Ron Reynolds
turn on debug for this log4j cateogory only - org.apache.axis.EXCEPTIONS - it 
is the category used for all faults
thrown on the server-side.

 I currently am getting the following fault returned from my Server when 
 communicating.

   soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
 xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
     soapenv:Body
   soapenv:Fault
     faultcodesoapenv:Server.userException/faultcode
     faultstringjava.lang.NullPointerException/faultstring
     detail
   ns1:hostname 
 xmlns:ns1=http://xml.apache.org/axis/;wiproxy/ns1:hostname
     /detail
   /soapenv:Fault
     /soapenv:Body
   /soapenv:Envelope


 It looks to me like there is an Null Pointer Exception that Axis is catching, 
 and turning into a Fault.

 Could somebody PLEASE tell me how or where in the chain I can get Axis to 
 give me a trace on this.  I have logs in the
 request/response flow, but apparently it doesn't get that far

 I'm not sure how i  can debug any problems like this if I can't get Axis to 
 give me more information.  It appears that
 if I turn log4j debug on, it may provide me the trace, but I'm filling up 
 disk space.  Also, I can't get it to fail
 when I turn it on.

 Is there even a handler that I can override for the express purposes of 
 examining the axis fault and logging it.  I'm
 at my wits end - help, please.

 Hopefully it's something shamefully simple that I'm missing.








Re: Uncaught Exception Traces - how to get Axis to tell me what they are

2005-10-03 Thread Vishist Mandapaka
Hi Paul,
 If the debugger
doesn't help you, try to debug over TCP connection. You can enable
debugging in the server. Let me know what server you are using and I
can let you know how to enable debugging. Once you enable debugging, a
TCP Port will open up and the server will print the port number on the
standard output. U can use debugging tools like JDebugger which will
attach to the TCP Port. Once attached, set code break points and you
can quickly realize where it is giving exception. This environment
setup might take a little while for you, but it pays to use proper
debugging tools as you can see the workflow.
thanks
vishist.On 10/3/05, Ron Reynolds [EMAIL PROTECTED] wrote:
turn on debug for this log4j cateogory only - org.apache.axis.EXCEPTIONS - it is the category used for all faultsthrown on the server-side. I currently am getting the following fault returned from my Server when communicating.
 soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsd=
http://www.w3.org/2001/XMLSchema xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance soapenv:Body soapenv:Fault
 faultcodesoapenv:Server.userException/faultcode faultstringjava.lang.NullPointerException/faultstring detail ns1:hostname xmlns:ns1=
http://xml.apache.org/axis/wiproxy/ns1:hostname /detail /soapenv:Fault /soapenv:Body /soapenv:Envelope It looks to me like there is an Null Pointer Exception that Axis is catching, and turning into a Fault.

Could somebody PLEASE tell me how or where in the chain I can get Axis
to give me a trace on this.I have logs in the request/response flow, but apparently it doesn't get that far
I'm not sure how ican debug any problems like this if I
can't get Axis to give me more information.It appears that
if I turn log4j debug on, it may provide me the trace, but I'm filling
up disk space.Also, I can't get it to fail when I turn it on.
Is there even a handler that I can override for the express purposes of
examining the axis fault and logging it.I'm at my wits end - help, please. Hopefully it's something shamefully simple that I'm missing.