| Key: |
RHQ-829
|
| Type: |
New Feature
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Blocker
|
| Assignee: |
Greg Hinkle
|
| Reporter: |
Greg Hinkle
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
RHQ Project
Created: 11/Sep/08 01:46 PM
Updated: 15/Dec/08 06:33 AM
|
|
| Component/s: |
None
|
| Fix Version/s: |
1.1
|
|
|
Time Tracking:
|
|
Original Estimate:
|
2 hours
|
|
|
Remaining Estimate:
|
2 hours
|
|
|
Time Spent:
|
Not Specified
|
|
|
|
|
Issue Links:
|
Relation
|
|
|
|
This issue Is Related To:
|
|
|
RHQ-912 JVM remoting - errors appear in agent when jvm is shut down
|
|
|
|
|
|
|
| Resolution Date: |
15/Sep/08 02:20 PM
|
| Date of First Response: |
30/Sep/08 03:24 PM
|
| Tester: |
Jeff Weiss
|
| VCS Revision: |
1,464
|
|
This feature is to add the automated discovery of a standalone JVM (1.5 or higher) that is running the platform mbean server and the built-in JMX Remoting functionality. It will discovery and key off of the command-line JMX Remoting properties. (specifically com.sun.management.jmxremote.port)
Unsure of whether we will be able to support SSL yet since I don't think it's supported in EMS yet, but will investigate.
An example test would be to start jconsole with these properties and then do a discovery:
java -jar -Dcom.sun.management.jmxremote.port=1500 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -jar /usr/java/jdk1.5.0_15/lib/jconsole.jar
We should be sure to restart the vm process and make sure its being discovered as the same process and reconnected/disconnected appropriately
|
|
Description
|
This feature is to add the automated discovery of a standalone JVM (1.5 or higher) that is running the platform mbean server and the built-in JMX Remoting functionality. It will discovery and key off of the command-line JMX Remoting properties. (specifically com.sun.management.jmxremote.port)
Unsure of whether we will be able to support SSL yet since I don't think it's supported in EMS yet, but will investigate.
An example test would be to start jconsole with these properties and then do a discovery:
java -jar -Dcom.sun.management.jmxremote.port=1500 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -jar /usr/java/jdk1.5.0_15/lib/jconsole.jar
We should be sure to restart the vm process and make sure its being discovered as the same process and reconnected/disconnected appropriately |
Show » |
|
JVM Remoting auto-discovery