Exception Root Cause Detection
Hello,
After some PurePath examination I noticed that the program does not show the real root cause exception but the triggered exceptions.
We have following Java application architecture for our tests:
After SOAP Webservice function call on Backend Webserver there was some custom thrown runtime NumberFormatException and following connection interception.
Following details were displayed by PurePath:
- SoapFault Exception on Web-Server
- HTTP Servlet Interception and SoapFault Exception on Backend Web-Server
As you can see there was not displayed the real root cause (NumberFormatException) for both Exceptions on Backend side.
Is there any possibility to see the real root cause?
And second question would be: Do you plan some new specific features for your product?
Tank you.
Aleksej,
Regarding your second question about new features: Are you looking for anything special or missing anything?
Of course our future versions will be updated with new technology support and improvements in terms of scalability and usability. Also there will be updates based on our customer's feedback and enhancement requests.
I can't give you an detailed roadmap at this stage though.
Reinhard
Thank you. It worked now.
Great to see that you have successfully installed dT and are getting PurePaths.
As to your question. Our Exception Sensor is configured in a way to DO NOT capture exceptions from the "java", "javax", and "sun" packages. Reason for that is because we typically see a lot of these exceptions being thrown and also handled withing frameworks, core libaries or the app server code itself. Good News is that you can configure the Exception Sensor to also capture these types of Exceptions.
Here is what you do
a) Edit your System Profile, e.g: double click on it in the Cockpit
b) Expand the section of your Application Server Tier
c) Select "Sensor Configuration"
d) click on Properties next to the Exception Sensor
Here you will see the list of Exceptions that are excluded from being captured. You can e.g: try to capture everything and see what you get. Once you Apply the changes in the System Profile or click OK to close the System PRofile Dialog these changes will take immediat effect - meaning - new PurePaths that come in will then show these additional exception.
Here are also some additional links to the doc: Exceptions and Java Exception Sensor
Let me know if this helps
Andi
