CentOS 5.7 x86_64, both Zabbix server and Java bridge are 2.0.1

Is there a workaround to re-enable the interface manually?

similar issue ZBX-5226 turned out to be a misconfiguration

I've checked ZBX-5226 already before, but I didn't touch the configuration before or after stopping/starting my Java gateway.
Further I have some hosts with JMX interfaces, where it still works fine, only interfaces where Zabbix tried to pull exactly at the time the Gateway was down, don't get green again.
When I track the JMX pulls in zabbix_server.log, I can see log entries like

5397:20120704:160254.989 In get_values_java() host:'myhost1' addr:'192.168.2.68' num:4

for hosts/interfaces working but I miss a log line for the the host/interface which is marked down. So I have the impression, Zabbix server doesn't even try to reach it.

Hi

Is there any progress on this issue?
This issue is pretty blocking for me. I have several hosts with a JMX interface and items which aren't polled anymore. The items itself are active but the interface is marked down. The java gateway doesn't report any connect attempts.
Is there any way to force re-enable the JMX interface?

Thanks

this issue not scheduled for short term currently. depending on where the interfaces are disabled, you can try restarting server/gateway, or looking at the database

can't reproduce with 2.0.2rc1 and openjdk 1.6.0_24

if i shut down the monitored java process, it shows up as down and then recovers properly when process is started up again.
if i shut down java gateway, it shows up as down and then recovers properly when gateway is started up again.

I found a workaround. I found the host's entry in the "hosts" table in the zabbix database, and changed jmx_disable_until to 0, changed jmx_available to 1, and jmx_error_from to 0. Restarted zabbix-server. Stuff started working again.

In my case bundles have become available, but on the monitor I see only "no data". In the database jmx_disable_until and jmx_error fields updates with new error values. Any ideas?

We have tried various timeout scenarios, but cannot reproduce the problem at the moment.

Those of you who still experience the problem with the latest versions, do you have a reliable way of reproducing it?

Would it be possible for you to run Java gateway with a "trace" debug level?

In order to increase the debugging level, change "info" to "trace" in lib/logback.xml:

<root level="info">
	<appender-ref ref="FILE" />
</root>

Similarly, in order to increase the maximum log file size, change "maxFileSize" parameter:

<triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
	<maxFileSize>5MB</maxFileSize>
</triggeringPolicy>

When the problem happens, is it possible to connect to the Java gateway? For instance, by telnetting to its port or running a debugging utility from Zabbix source code like follows:

echo '{"request":"java gateway internal","keys":["zabbix[java,,ping]","zabbix[java,,version]"]}' | misc/debug/sender.pl -h 127.0.0.1 -p 10052 -i -

If there is anybody that still experiences this problem with the latest gateway versions, please tell us.

For those of you having this problem with JBoss, please check whether ZBX-8579 solves your problem.

Looks like ZBX-8839 might explain the problem people were having here.

There is no response, so closing the issue as "Cannot Reproduce". Fix in ZBX-8839 has just been merged, too. Please reopen if the issue appears again with ZBX-8839 fix in place.

Hi,

Confirmed the bug

OS: Red Hat Enterprise Linux Server release 6.6 (Santiago)
Zabbix-server: 2.0.1
java-gateway: 2.0.0

After this (see near) works fine!

mysql> select host, jmx_disable_until, jmx_available,  jmx_errors_from from hosts where host="srv14";
+-----------+-------------------+---------------+-----------------+
| host      | jmx_disable_until | jmx_available | jmx_errors_from |
+-----------+-------------------+---------------+-----------------+
| srv14 |        1583430260 |             1 |      1426054531 |
+-----------+-------------------+---------------+-----------------+
1 row in set (0.00 sec)

mysql> update hosts set jmx_disable_until=0, jmx_available=1, jmx_errors_from=0 where  host="srv14"; 
Query OK, 1 row affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0


mysql> select host, jmx_disable_until, jmx_available,  jmx_errors_from from hosts where host="srv14";
+-----------+-------------------+---------------+-----------------+
| host      | jmx_disable_until | jmx_available | jmx_errors_from |
+-----------+-------------------+---------------+-----------------+
| srv14 |                 0 |             1 |               0 |
+-----------+-------------------+---------------+-----------------+
1 row in set (0.00 sec)

& RESTART zabbix_server and java_gateway

Neiro, as suggested in my last comment above, please try the latest version with ZBX-8839 fix included. Versions 2.0.0 and 2.0.1 are too old.