Java application monitoring basics

[Former Member]

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.

[hemanth2]

Hi Harold,

Hope you are doing good.

Basically when you feel that the server performance is low, take 5-6 dumps on each of the server node and then compare the dumps to reach on a valid conclusion as to which application

is responsible. If an application is causing deadlock issues, it will be in a "waiting for monitor entry" state in the dumps. There can be a case that only 1 or 2 server nodes are affected. In such a case, you will need to use note 1589567 and check the behaviour of individual nodes.

Then when the application is identified,  open a telnet session to the engine as per note 531293, jump to the server node and unlock the application:

> telnet <host> 5NN08
> jump 0
> add deploy
> unlock_app sap.com/mss~exp (for example)

Refer to note 710966 for details. Visual admin-> server-> services-> locking adapter also gives some
info on the locks and how the can be deleted in critical cases.

If you are planning a server restart, deleting the locks is a better option first.

Please check:

http://wiki.sdn.sap.com/wiki/x/VYZ3Cw

SAP Note No. 710154-How to create a thread dump for the J2EE Engine

Thank you and have a nice day :).

_____________
Kind Regards,
Hemanth

[michael_ruth3]

Harold,

Why not setup CCMS monitoring through solution manager and let those reports inform you of your bottlenecks?