Yes. It is with some JASPER library changes in Tomcat which affected the NewRelic agents. It was fixed in NewRelic agent 8.2.0. In our case we have newrelic agent 7,4.x ., So it failed.
For a temporary measure we disabled the new relic browser monitoring and moved on. (Ours is not a UI app) You can check the fixes section of release notes https://docs.newrelic.com/docs/release-notes/agent-release-notes/java-release-notes/java-agent-820/ https://github.com/newrelic/newrelic-java-agent/pull/1225 வெள்., 1 செப்., 2023, பிற்பகல் 3:02 அன்று, Tim N <tnti...@gmail.com> எழுதியது: > Fixed by upgrading New Relic to 8.5.0! > > Other environments had this upgraded, but not the failing one. > > On Fri, Sep 1, 2023 at 5:26 PM Torsten Krah <krah...@gmail.com> wrote: > > > Am Freitag, dem 01.09.2023 um 15:18 +1000 schrieb Tim N: > > > We're seeing this too, but not in all our environments. We also use > > > NewRelic. > > > > Does it happen without NewRelic too? If not, better ask NewRelic about > > that problem. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > > -- நன்றி, அருள்.
