Skip to Content
0
Former Member
Jul 12, 2012 at 03:50 PM

Java application monitoring basics

15 Views

Hi Expets

I'm a Basis person, and I'm getting more invovled with supporting NW java based systems that are running custom developed Java code. The contractors are developing programs currently. We have the Wily tool installed and setup to monitor our NW 7.3 CE system. Twice now, we have had the system basically get really slow, and response time get really bad. It is as if something was looping in the system. We took the drastic measure of stoping and restarting the system. I'm thinking with all of the tools there has to be a better way. Shouldn't I be able to use Wily or built in stuff on the Java stack to find the offending process/thread/user and kill that user and not have to shutdown the whole system. I'm thinking ahead to when we put this application into production. I need to be able to find a user runing a process/task that is consuming the system and kill it.

Any and all pointers and links and information would be appreciated.