-
New Feature Request
-
Resolution: Fixed
-
Minor
-
2.0.0
-
Sprint 2, Sprint 3, Sprint 4, Sprint 5, Sprint 6, Sprint 7, Sprint 8, Sprint 9, Sprint 10, Sprint 11
-
5.6
Currently jmx endpoint is hardcoded into JMXItemChecker.java:
service:jmx:rmi:///jndi/rmi://" + conn + ":" + port + "/jmxrmi"
However some applications use different endpoints for jmx management, for example jboss as7:
service:jmx:remoting-jmx://conn:port
Suggestion is to make this endpoint configurable per host in the frontend on the CONFIGURATION OF HOSTS screen.
- is duplicated by
-
ZBXNEXT-2914 unable to get values from recent WebLogic, e.g. 12c, because of fixed url
- Closed
-
ZBXNEXT-1289 Problem Configurable JMX Endpoint on jboss 7
- Closed
-
ZBXNEXT-1307 Add field for manual entry of jmx-url instance name, instead of hardcoded "jmxrmi".
- Closed
-
ZBXNEXT-1338 JMXMP support
- Closed
-
ZBXNEXT-1713 Zabbix Java / Host Interface / add habitilty to specify an url instead of host
- Closed
-
ZBXNEXT-2906 Enable support for Wildfly which uses http-remoting-jmx instead of rmi
- Closed
-
ZBX-9552 Name in URL JMX Supervision with Zabbix
- Closed
-
ZBX-4521 Allow full JMX service URLs not just the "default" ones
- Closed
-
ZBX-10975 Expand JMX monitoring capabilities
- Closed
1.
|
Subtask: Documentation for configurable JMX endpoints | Closed | Unassigned |