Apr 12th, 2010, 11:37 AM
Logging exception stack traces - stack traces are lost
We have extended SoapFaultMappingExceptionResolver to log all exceptions that get caught by the framework, but we have noticed that these exceptions do not contain any stack trace information and are therefore of very little use. We are using PayloadRootAnnotationMethodEndpointMapping with @Endpoint annotation on our service methods. It looks like the stack traces are getting lost inside aop somewhere.
We can recreate the issue by explicitly throwing a NullPointerException from withn our @Endpoint method - this exception contains stackTrace=null when we try to log it in the exception resolver.
Questions is - is there any way to preserve the stack trace? And is there a better way to log all exceptions caught by the framework?
Tags for this Thread