Discussion Feed

dhyunkang · ‎03-30-2015

Thank you for your answer. The JVM I tested is already in the scope of monitoring. The JVM is in the chain of business transactions. I wanted to test how I can get notifcation from the crash so that I can execute some script. I think it may be related with some system environments like OS version, system libraries, and etc. I could not get enough clue from the log of machine agent. How can I investigate further? Thanks again.

dhyunkang · ‎03-26-2015

HI all, I tried to detect JVM Crash events. First, I configured Policy for JVM Crash as mentioned in documentation like the attachment. And I started MachineAgent. I killed JVM with -9 option. Nothing was reorted in Events screen. When I restarted the JVM, JVM restarted event was displayed. And when JVM is killed, this message was logged in machine-agent.log file. [Agent-Monitor-Scheduler-3] 27 Mar 2015 11:34:14,919 INFO SigarAppAgentMonitor - Detected that JVM for PID 15572 is no longer active My platform is CentOS 5.5 64 bit. I use JDK 1.6 32 bit version for both AppServerAgent and MachineAgent. For controller, I use JDK 1.7.0_55 64 bit version. Can anybody help me to fix this? Regards, Scott Kang

Date Registered	‎12-17-2012 03:29 AM
Date Last Visited	‎03-07-2017 09:44 AM
Total Messages Posted	2
Total Kudos Received	1

Discussion Feed

Re: MachineAgent does not detect JVM Crash

MachineAgent does not detect JVM Crash