Did anyone encounter this error on any of your WAS monitored applications?
This application is running on a WAS 7.6 (which is not supported, I know) but all other monitored applications work fine. I even searched for other uses of the "ebanking.framework.filters.EncryptionFilter.doFilter" method that generates this issue and all others work. Except this one.
I have to mention that this WAS process was formerly monitored with AppMon and had no issues. Yesterday we deactivated the AppMon agent and installed OneAgent on the host.
Do you guys have any ideea on how could I resolve this?
Root causes for requests that failed with HTTP 500 - Internal Server Error 100 % were caused by javax.servlet.http.HttpServletResponse.setStatus Exception messages of javax.servlet.http.HttpServletResponse.setStatus HTTP ***** setStatus called Stacktraces of exceptions java.lang.Thread.getStackTrace (Thread.java:1070) com.compuware.apm.agent.introspection.servlet.ServletIntrospection.updateResponseStatusOnTraceTag (ServletIntrospection.java:968)[+] com.ibm.ws.webcontainer.srt.SRTServletResponse.setStatus (SRTServletResponse.java)[+] javax.servlet.http.HttpServlet.service (HttpServlet.java:738)[+] com.ibm.ws.webcontainer.servlet.ServletWrapper.service (ServletWrapper.java:1661)[+] ebanking.framework.filters.EncryptionFilter.doFilter (EncryptionFilter.java:104) com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter (FilterInstanceWrapper.java:190)[+] com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest (CacheServletWrapper.java:91)[+] com.ibm.ws.webcontainer.webapp.WebApp.handleRequest (WebApp.java:3954)[+]
Answer by Joseph H. ·
I agree with Dave, just because we're in the stack trace does not automatically implicate our agent.
In this situation the stack trace tells us the thread was processing a web request, specifically setting the response status code. Dynatrace instruments this code to fiddle with this response and immediately a stack trace is involved, which makes me suspicious that in this situation we are the root cause of the exception.
I would open a support case, but since WAS 7.6 is not supported, this makes it challenging and likely they won't work your case.
Answer by Dave M. ·
My take on this is that the presence of our agent in a stacktrace is not usually indicative of us causing the problem, but simply a side effect of our code being hit while intercepting the the information we gather in the code. Are you suspecting us of causing the exception and not just reporting it?
Check what has changed for SaaS, Managed, and Dynatrace API in version 170.
See release notes
Join our hands-on introduction to Dynatrace's brand new IBM System z Mainframe Support!
Wednesday, June 12, 2019
Learn how to set business hours per application, manage report users from a single dashboard, use the configuration REST API, and many more!
Wednesday, June 12, 2019
Hiding Application/Service? 1 Answer
Memory Utilization vs Used memory 0 Answers