ing-arriola
commented
6 years ago UPDATE:
I have continued reviewing my test application and likewise other applications with the aim of identifying what happens with this problem of not showing the errors and I have a new assumption with a much stronger foundation: I have reviewed some transactions with errors and for example I have some which show me the detail of being a "Handled Exception", which was done at the time of development .... but the transactions that I know are errors and not the classifies as errors by Pinpoint it turns out that they are "Unhandled Exceptions" ... which are effectively reported in the WebLogic Log as errors ... so I have the slight feeling that Pinpoint can only classify a transaction as one that has an error in the case that the developer has thought in advance to add the controlled exception; for example in the case of an exception of type SQL, Java requires that when using JDBC there are some details such as entering values in a table that must have the "Handled Exception" to allow me to compile. On the other hand there are errors that could happen as the case I gave as an example above where the sum between a number and a letter, where logically I know it will be an error and will be reflected in the WebLogic Log or any other WAS. but the fact that I do not put that operation of sum in a Try ... Catch does not affect the moment of compilation .... the correct thing would be that I as a developer foresee that situation and enter the sum in a Try ... Catch with something like "IllegalArgumentException" ... so it would be a great help to give feedback on this topic; Given that there are other APM that apparently are also trying to observe this issue, I attach a link to this.
In advance thank you very much for the help.
Xylus
jaehong-kim
Ankcy
Description
Recently I have done extensive tests with Pinpoint to verify the way it shows the errors, that is to say if it is more comfortable for a developer to have access to the errors from Pinpoint instead of having to check the WAS Weblogic Log where I have I have unfortunately found that Pinpoint is not able to classify an HTTP 500 error precisely as an error, when reviewing the call tree I realized that the error transaction was actually received by Pinpoint but it is not marked as an error ... Why is this happening?
In my case I have thought about three hyposthesis I mention them:
The Pinpoint sampling rate was lower than the speed at which the transactions occurred ... for me this is false given that the transactions with error were in the Call Tree.
The error codes were not correctly configured ... this is also false given that you check the Pinpoint.config file and have the following line configured: profiler.http.status.code.errors = 5xx
I do not know if the alteration of the Log4J file in the route: Agent / lib / log4J.xml has some weight in the matter ....
The only thing that is clear to me is that Pinpoint does not classify HTTP 500 errors as such, but rather only as transactions without any particular feature.
By the way i am wondering... What Pinpoint sees as an "error"???
I attach the WebLogic Log to support what I said; any help will be happily received and in advance thank you very much.
Please compare the attached image with the Log in the part where I have highlighted in order to verify that effectively when WebLogic detects an error, Pinpoint does not see it as an HTTP error.
Psdt: The test application is a small calculator that performs the basic operations.
2018-05-21 10:36:26 INFO profiler.weblogic.enable=true 2018-05-21 10:36:26 INFO profiler.weblogic.excludeurl= 2018-05-21 10:36:26 INFO profiler.weblogic.tracerequestparam=true <May 21, 2018 10:36:26 AM CST>
<May 21, 2018 10:36:26 AM CST>
<May 21, 2018 10:36:27 AM CST>
<May 21, 2018 10:36:27 AM CST>
<May 21, 2018 10:36:27 AM CST>
<May 21, 2018 10:36:57 AM CST>
<May 21, 2018 10:36:57 AM CST>
<May 21, 2018 10:36:57 AM CST> <Starting "async" replication service with remote cluster address "null">
<May 21, 2018 10:36:57 AM CST> <Channel "Default" is now listening on 172.23.112.192:7004 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<May 21, 2018 10:36:57 AM CST> <Started WebLogic Managed Server "test3" for domain "my_domain" running in Production Mode>
<May 21, 2018 10:36:58 AM CST>
<May 21, 2018 10:36:58 AM CST>
<May 21, 2018 10:37:51 AM CST> <[ServletContext@1128068367[app:test_linux module:test_linux.war path:/test_linux spec-version:2.5]] Servlet failed with Exception
java.lang.NumberFormatException: For input string: "13161387Y"
at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2043)
at sun.misc.FloatingDecimal.parseDouble(FloatingDecimal.java:110)
at java.lang.Double.parseDouble(Double.java:538)
at jsp_servlet.__controlador._jspService(__controlador.java:75)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
Truncated. see log file for complete stacktrace
Environment
Additional Info