[#ZBX-4521] Allow full JMX service URLs not just the "default" ones

[ZBX-4521] Allow full JMX service URLs not just the "default" ones Created: 2012 Jan 05 Updated: 2017 May 30 Resolved: 2013 Apr 20
Status:	Closed
Project:	ZABBIX BUGS AND ISSUES
Component/s:	Java gateway (J)
Affects Version/s:	1.9.8 (beta)
Fix Version/s:	None

Type:

Problem report

Priority:

Major

Reporter:

Haroon Rafique

Assignee:

Unassigned

Resolution:

Duplicate

Votes:

Labels:

jmx

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Attachments:

zabbix-2.0.5-jmx_url.diff

Issue Links:

Duplicate
duplicates	~~ZBXNEXT-1274~~	Configurable JMX Endpoint	Closed

Description

It would be great if Java Gateway would allow full JMX service URLs and not just the "default" ones. The current JMX URLs supported by zabbix look like:

service:jmx:rmi:///jndi/rmi://192.168.50.102:9004/jmxrmi

A full JMX service URL might look like:

service:jmx:rmi://rmiHost:rmiPort/jndi/rmi://namingHost:namingPort/jndiPath

So, in our case, jndiPath is not always jmxrmi and rmiHost (usually same as namingHost) is also specified. In addition, rmiPort is different than namingPort. A concrete example is:

service:jmx:rmi://host1:9004/jndi/rmi://host:1099/myjmx

Comments

Comment by Haroon Rafique [ 2012 Jan 05 ]

service:jmx:rmi://rmiHost:rmiPort/jndi/rmi://namingHost:namingPort/jndiPath

Looking at the above service URL, if the following conditions happen:

1. rmiHost and rmiPort are not specified
2. jndiPath is not specified

we can simply end up with the canonical url service:jmx:rmi:///jndi/rmi://namingHost:namingPort/jmxrmi and everyone is happy.

Cheers.

Comment by Axel Wienberg [ 2013 Apr 17 ]

more use cases for full JMX service URLs:

support for connecting to IBM Websphere Application server, which uses a URL such as service:jmx:iiop://<HOSTNAME>:9100/jndi/JMXConnector
support for connecting via jmxmp - service:jmx:jmxmp://myhost:5555
support for using a fixed rmiPort, to better traverse firewalls - see http://tomcat.apache.org/tomcat-7.0-doc/config/listeners.html#JMX_Remote_Lifecycle_Listener_-_org.apache.catalina.mbeans.JmxRemoteLifecycleListener

Comment by dakol [ 2013 Apr 19 ]

Quick & Dirty patch to allow full JMX url in Interface DNS using prefix url://

increase interface>dns columns from 64 to 256 bytes
CHostInterface.php:checkDns() allow url:// prefix on DNS
Zabbix Java detect url:// and use it as is

example with OpenMQ:
url://service:jmx:rmi://host1/jndi/rmi://host1:8688/host1/7676/jmxrmi

Comment by Marc [ 2013 Apr 19 ]

Does this issue differ from ~~ZBXNEXT-1274~~?

Comment by richlv [ 2013 Apr 20 ]

indeed, let's continue in ~~ZBXNEXT-1274~~

Generated at Wed Dec 24 14:29:24 EET 2025 using Jira 10.3.13#10030013-sha1:56dd970ae30ebfeda3a697d25be1f6388b68a422.

[ZBX-4521] Allow full JMX service URLs not just the "default" ones Created: 2012 Jan 05 Updated: 2017 May 30 Resolved: 2013 Apr 20