[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: | 5 |
Labels: | jmx | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: | zabbix-2.0.5-jmx_url.diff | ||||||||
Issue Links: |
|
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 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:
|
Comment by dakol [ 2013 Apr 19 ] |
Quick & Dirty patch to allow full JMX url in Interface DNS using prefix url://
example with OpenMQ: |
Comment by Marc [ 2013 Apr 19 ] |
Does this issue differ from |
Comment by richlv [ 2013 Apr 20 ] |
indeed, let's continue in |