差異處
這裏顯示兩個版本的差異處。
|
java:servicewrapper:wrapperactionserver [2017/10/11 18:04] tony [Reference] |
java:servicewrapper:wrapperactionserver [2023/06/25 09:48] |
||
|---|---|---|---|
| 行 1: | 行 1: | ||
| - | {{tag>java Java_Service_Wrapper}} | ||
| - | ====== WrapperActionServer ====== | ||
| - | ===== Problem ===== | ||
| - | 某天有個運氣很好的同事，測試某個功能時，發生Service自己異常中止的問題。經過初步trace，發現那台機器被[[https://www.tenable.com/products/nessus-vulnerability-scanner|Nessus]]掃瞄過後，JVM就異常中止了。 | ||
| - | <code> | ||
| - | ERROR | wrapper | 2017/10/06 16:42:16 | JVM exited unexpectedly. | ||
| - | </code> | ||
| - | ===== How to resolve? ===== | ||
| - | ==== Trace ==== | ||
| - | 首先我將wrapper log level改為DEBUG，並打開了wrapper ping jvm的log: | ||
| - | <code> | ||
| - | wrapper.logfile.loglevel=DEBUG | ||
| - | wrapper.ping.alert.loglevel=DEBUG | ||
| - | </code> | ||
| - | 接著發現訊息出現: | ||
| - | <code> | ||
| - | INFO | jvm 1 | 2017/10/06 16:42:13 | WrapperManager: WARNING: Making JVM appear to be hung... | ||
| - | </code> | ||
| - | 這個問題看起來是外力讓wrapper造成了jvm的hang。 | ||
| - | ===== Reference ===== | ||
| - | * [[https://www.tenable.com/products/nessus-vulnerability-scanner|Nessus]] | ||
| - | * [[https://wrapper.tanukisoftware.com/doc/english/example.html|Running the TestWrapper Example Application]] | ||
| - | * [[https://wrapper.tanukisoftware.com/doc/english/prop-jvm-kill-delay.html|thread dump的問題]] | ||
| - | * [[https://wrapper.tanukisoftware.com/jdoc/org/tanukisoftware/wrapper/WrapperActionServer.html|javadoc - WrapperActionServer]] | ||
