[ZBXNEXT-2906] Enable support for Wildfly which uses http-remoting-jmx instead of rmi Created: 2015 Aug 18 Updated: 2018 Jan 03 Resolved: 2015 Aug 19 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Java gateway (J) |
Affects Version/s: | 2.4.6 |
Fix Version/s: | None |
Type: | Change Request | Priority: | Trivial |
Reporter: | Marcos K. Sakamoto | Assignee: | Unassigned |
Resolution: | Duplicate | Votes: | 2 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
Description |
Zabbix Java Gateway only supports JMX connection through RMI. Please, enable support for http-remoting-jmx. |
Comments |
Comment by Marc [ 2015 Aug 18 ] |
Could it be a duplicate of Well, not sure regarding Wildfly and http-remoting-jmx but for JBoss EAS 6 and remoting-jmx it does the trick (in addition to adding some jboss remoting-jmx JARs of course). |
Comment by Marcos K. Sakamoto [ 2015 Aug 18 ] |
It's slightly different as Wildfly uses WebSocket support to upgrade the HTTP protocol for JMX communication. url = new JMXServiceURL("service:jmx:http-remoting-jmx://" + conn + ":" + port); Note the http in connection string. But we have changed the code in a similar way as a workaround to this problem. |
Comment by richlv [ 2015 Aug 19 ] |
it does seem to be a duplicate of |
Comment by richlv [ 2018 Jan 03 ] |
wildfly jmx also discussed in ZBXNEXT-4133 |