[ZBX-20454] WildFly JMX Monitoring - not supported protocol Created: 2022 Jan 18  Updated: 2024 Apr 05  Resolved: 2022 Jan 19

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Java gateway (J), Proxy (P)
Affects Version/s: 4.0.37
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Damian Cancela Assignee: Igor Gorbach (Inactive)
Resolution: Commercial support required Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Hello,

 

im having an issue with Zabbix JMX monitoring, maybe you can help me to troubleshoot this.

I have a Zabbix Server running with some Zabbix Proxies, in each instance we have Java Gateway component to monitor different JMX hosts

Zabbix version is the same Server or Proxies, 4.4.8. Solution is installed in different hosts with Red Hat Enterprise Linux 6.10 Santiago OS's.

We never had any issues with normal JMX items (rmi protocol) like service:jmx:rmi:///jndi/rmi://

But now we need to monitor a WildFly 21 server, is working fine if we connect to the Wildfly JMX using Jconsole tool from my windows laptop opening the Jconsole importing the wildfly jboss-client.jar class, running from cmd something like

 

Move into jconsole exe location

cd C:\Program Files (x86)\Java\jdk1.8.0_211\bin

Execute Jconsole

jconsole -J-Djava.class.path="C:\Program Files (x86)\Java\jdk1.8.0_211\lib\jconsole.jar;C:\jboss-client.jar"

 

It work ok using these two connection strings

service:jmx:remote+http://10.216.78.34:9990

service:jmx:http-remoting-jmx://10.216.78.34:9990

 

BUT!

If i test this from Zabbix. if i create an item in zabbix with any of those connection strings i got an error saying that the http protocol is not supported

in zabbix_java.log file i see this error

2022-01-18 09:26:24.563 [pool-1-thread-18] WARN  com.zabbix.gateway.SocketProcessor - error processing request, item "jmx["jboss.system:type=ServerInfo","AvailableProcessors"]" failed: Unsupported protocol: remote+http: service:jmx:remote+http://10.216.78.34:9990

 

Ive created the item with this JMX endpoint service:jmx:remote+http:///jndi/rmi://\{HOST.CONN}:{HOST.PORT}/jmxrmi, or similar strings.

 

I've tried doing the jar files thing that is showed here at Custom endpoint example with JBoss EAP 6.4 part
 https://www.zabbix.com/documentation/4.0/en/manual/config/items/itemtypes/jmx_monitoring

but didn't work, maybe is not the same, but i think i need to do something similar.

 

Not sure if you can help me with this. Thanks!



 Comments   
Comment by Igor Gorbach (Inactive) [ 2022 Jan 19 ]

ZBX - is a bug tracker for identifying and fixing some issues in Zabbix functionality
Your problem is related to WildFly misconfiguration for the Zabbix connection and we're not able to fix the mentioned issue on this project.

Custom JMX Implementation is just an example and it has not involving all the cases with custom JMX endpoint
You can get some help in 
Zabbix International Community in Telegram

or

Zabbix Forum

Or, you're able to get commercial support

 

Comment by Damian Cancela [ 2022 Jan 19 ]

Hi Igor, thanks!

Are you sure? Because the JMX is open in wildfly instance and i can connect to it with Jconsole, so i think the access is fine, ports are open and the jmx credentials are ok as well. It seems like java gateway is not able to use http-remote protocol, just rmi. 

Comment by dimir [ 2024 Apr 05 ]

damiancancela Have you tried any of the latest versions to see if it works?

Generated at Sat Apr 26 06:08:14 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.