In one of our WASt 8.5.x application servers we can have more than 100 applications deployed. We know they share the JVM, right now 1.7 version, which means that all the deployed applications in the server instance run on top of a single JVM.

We use different tools to monitor the application server. For example, IBM Heap Analyzer and Thread Monitor Dump Analyzer tools to inspect Java Core Dump files. To monitor the application server while running we have tried Tivoli Performance Viewer, Lucierna, New Relic, VisualVM, ...

The thing is that we can NOT see memory usage data for an individual application deployed in the server. These tools only display global information about memory usage so we can see at a certain moment that memory is almost full, but we can NOT identify which application or applications are consuming more memory and causing the problem.

Does any IBM APM tool provide this feature? I am not sure if I am explaining the issue clearly: we would like to see how much memory is being used by each individual application deployed on a single server instance.

Please try the IBM Health Center:  

https://www.ibm.com/support/knowledgecenter/en/SS3KLZ/com.ibm.java.diagnostics.healthcenter.doc/homepage/plugin-homepage-hc.html

This definitely reminds me of my days as an IT rookie when a colleague saved all his spreadsheet calculations in just one file.

As fas as I know there is no reliable way to find out how much heap is used by a specific application. So how about singling them out? And migrating to Liberty once you have thought about it.

Regards Peter

As Peter said - none of the standard tools allow you to monitor the heap utilization on a per application basis. You'd have to do some profiling work (for example with HealthCenter) as suggested by Eric. This however requires in depth knowledge of the application as an application might use for example dynamic caching to store data which might / might not be shared with other applications. You'd also need to consider utilization of back-end adapters etc.

Otherwise if you suspect a certain application of using too much heap you might consider mapping that application to a dedicated server so that you can monitor the applications behavior there.

The hard way will be to take HEAP Dump snapshot and check which object are taking the much of the heap and from that you can find out which application might be the culprit.

Other way , ofcourse is tedious to check one application at a time and load your app server.  In my experience I did came across a tool - Dynatrace which could track your live transaction and possibly the memory consumed( again objects ).  But this live trasactions could provide you a hint as how much heap and which object are causing it. Unless your applications package name are not different and their is no way to differentiate as which object belongs to which class and application.