| Summary: | Wrong wiki about jconsole usage | ||
|---|---|---|---|
| Product: | [RT] Jetty | Reporter: | Missing name <nikolay.rychkov> |
| Component: | server | Assignee: | Jan Bartel <janb> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | janb, jetty-inbox, nikolay.rychkov |
| Version: | unspecified | ||
| Target Milestone: | 7.5.x | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Missing name
Resolved. Changed runline to: java -Dcom.sun.management.jmxremote -jar start.jar etc/jetty-jmx.xml as jmx is an OPTION that is defined by default in start.ini, and therefore you only need to specify the jetty-jmx.xml file on the command line. Note that you can also remove the -Dcom.sun.management.jmxremote and uncomment the appropriate lines in start.ini instead. thanks Jan Thank you. The problem was in ESET NOD32. It blocks jconsole connection. Wiki should consider this trouble. Updated wiki. To tell the truth I don't see any firewall consideration in wiki. http://wiki.eclipse.org/Jetty/Howto/Run_Jetty_with_JConsole#Connecting_to_your_server_process The intro says: "When following the instructions given below, please also ensure that you make any necessary changes to any anti-virus software you may be using which may prevent jconsole from running." Jan |