Zabbix Java Gateway Help

[tomtomclub]

We originally installed Zabbix server on Centos 6 using the rpm from the Zabbix website. Later we realized we needed to install the Java gateway, and found a way of doing it without compiling it using packages put together by Zabbixzone. I ran the install and it seemed to work fine.

What's happening:
I add a JMX agent item to a server that is already running and using the Zabbix agent. As soon as I select JMX Agent from the "Type" dropdown the "Select" button on the Key line greys out. I manually input a key. I originally tried "jmx["java.lang:type=Memory","HeapMemoryUsage.used"]" straight from the 2.0 manual, and then tried something simpler (jmx["java.lang:type=Runtime",Uptime]). No matter what, the JMX icon never turns green, and I never receive any info for the host.

Troubleshooting:
-I've verified that the Zabbix server is listening on port 10052. I can telnet to port 10052 on that server as well.

-I've verified that I can get the JMX connections to my clients by using jconsole from my laptop and jmxterm from the Zabbix server itself.

-I've checked the log for the Java gateway. It says the server started, is listening on port 10052 on all interfaces.

-I turned on debugging on the Zabbix server in logback.xml and got an additional line (only one) that says:

2013-10-01 20:08:10.852 [pool-1-thread-1] WARN com.zabbix.gateway.SocketProcessor - error processing request
java.io.EOFException: null com.zabbix.gateway.BinaryProtocolSpeaker.getReques t(BinaryProtocolSpeaker.java:56) ~[zabbix-java-gateway-2.0.8.jar:na]
at com.zabbix.gateway.SocketProcessor.run(SocketProce ssor.java:51) ~[zabbix-java-gateway-2.0.8.jar:na]
at java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1146) [na:1.6.0_24]

-I get nothing in the agent log on the client side.

Any tips?

[tomtomclub]

Never mind.

[tiarnaigh]

Hi tomtomclub.
Did you manage to get this working since? If so, can you please post what steps you took to resolve?

Thanks,
M

[fletch]

Hi
I've got the same problem. What was your solution to fix this bug?