Splunk AppDynamics

We converted our application from JBoss to Tomcat and now having heap utilization/ GC problems

Dan_Hillman
Explorer

We converted our application from JBoss to Tomcat and now having heap utilization/ GC problems.

Has anyone run across this scenario?

Labels (1)
0 Karma

Morelz
Motivator

Hi Dan

Can you provide more detail around your questions?

From my understanding, your application has been converted/upgraded/changed from Jboss to Tomcat Framework correct?

Are you stating that AppDynamics is causing heap utilization/ GC problems? If so can you advise where it indicates that AppDynamics is the cause of this? 

Ciao

Dan_Hillman
Explorer

This is not an Appdynamics issue. Our Customer migrated from using linux jboss to linux Tomcat. Their application did not have memory issues when running on jboss, but now that they have migrated over to Tomcat they are having memory problems. I was just curious if anyone has ran across this same scenario and had any insight on what they found troubleshooting this.

0 Karma

Morelz
Motivator

Thanks for the response.

Yeay, best would be to use AppDynamics to see if you can identify the Heap Issue. As well as trigger heap/Thread dumps for analysis which should point them into the right direction as to what is causing the problem

0 Karma

Dan_Hillman
Explorer

Yes, of course. I have already started my troubleshooting.

Is there anyone out there that has experienced this same type of scenario?

0 Karma
Get Updates on the Splunk Community!

Splunk Decoded: Service Maps vs Service Analyzer Tree View vs Flow Maps

It’s Monday morning, and your phone is buzzing with alert escalations – your customer-facing portal is running ...

What’s New in Splunk Observability – September 2025

What's NewWe are excited to announce the latest enhancements to Splunk Observability, designed to help ITOps ...

Fun with Regular Expression - multiples of nine

Fun with Regular Expression - multiples of nineThis challenge was first posted on Slack #regex channel ...