差異處
這裏顯示兩個版本的差異處。
| Both sides previous revision 前次修改 下次修改 | 前次修改 | ||
|
java:servicewrapper:wrapperactionserver [2017/10/11 20:44] tony |
java:servicewrapper:wrapperactionserver [2023/06/25 09:48] (目前版本) |
||
|---|---|---|---|
| 行 5: | 行 5: | ||
| ===== How to resolve? ===== | ===== How to resolve? ===== | ||
| ==== Trace ==== | ==== Trace ==== | ||
| - | 經過初步trace，發現那台機器被[[https://www.tenable.com/products/nessus-vulnerability-scanner|Nessus]]掃瞄過後，JVM就異常中止了: | + | 經過初步trace，發現那台機器被[[https://www.tenable.com/products/nessus-vulnerability-scanner|Nessus]]掃瞄過後，JVM就異常中止: |
| <code> | <code> | ||
| ERROR | wrapper | 2017/10/06 16:42:16 | JVM exited unexpectedly. | ERROR | wrapper | 2017/10/06 16:42:16 | JVM exited unexpectedly. | ||
| 行 20: | 行 20: | ||
| 這個問題看起來是Nessus連線讓wrapper造成jvm hang住。 | 這個問題看起來是Nessus連線讓wrapper造成jvm hang住。 | ||
| ==== WrapperActionServer ==== | ==== WrapperActionServer ==== | ||
| + | 從WrapperActionServer的javadoc中得知，它可以綁定某個port提供以下功能: | ||
| + | <code> | ||
| + | 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) | ||
| + | </code> | ||
| + | 預設情況下是disable的；但假如你都設為enable，就會發生我們所遇到的慘劇。所以怎麼解決? 只要enable需要的功能即可。\\ | ||
| + | \\ | ||
| + | 其實我個人並不推薦使用wrapper這個功能，因為有心人士很容易就把你系統給搞掛了。 | ||
| ===== Reference ===== | ===== Reference ===== | ||
| * [[https://www.tenable.com/products/nessus-vulnerability-scanner|Nessus]] | * [[https://www.tenable.com/products/nessus-vulnerability-scanner|Nessus]] | ||
