WrapperActionServer

某天有個運氣很好的同事，測試某個功能時，發生Service自己異常中止的問題。

經過初步trace，發現那台機器被Nessus掃瞄過後，JVM就異常中止了:

ERROR  | wrapper  | 2017/10/06 16:42:16 | JVM exited unexpectedly.

於是我將wrapper log level改為DEBUG，並打開了wrapper ping jvm的log:

wrapper.logfile.loglevel=DEBUG
wrapper.ping.alert.loglevel=DEBUG

最後發現訊息出現:

INFO   | jvm 1    | 2017/10/06 16:42:13 | WrapperManager: WARNING: Making JVM appear to be hung...

這個問題看起來是Nessus連線讓wrapper造成jvm hang住。

從wrapper的javadoc中得知，它提供了以下功能:

S : Shutdown cleanly.
H : Immediate forced shutdown.
R : Restart
D : Perform a Thread Dump
U : Unexpected shutdown. (Simulate a crash for testing)
V : Cause an access violation. (For testing)
G : Make the JVM appear to be hung. (For testing)

• Nessus
• Running the TestWrapper Example Application
• thread dump的問題
• javadoc - WrapperActionServer

---