Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-14364

Possible Memory Leak zabbix-java-gateway

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Won't fix
    • Icon: Minor Minor
    • None
    • 3.4.8
    • Java gateway (J)
    • None
    • Zabbix-Server 3.4.9
      Zabbix-Proxy 3.4.8 (Active)
      Zabbix-Java-Gateway 3.4.8
      OS: Centos7 OpenVZ Container
      Java: OpenJDK 1.8.0_161

      Hi,

      I got 2 Zabbix-Java-Gateways running with additional jar-files for providing additional to RMI the protocols "remoting-jmx" (for JBoss EAP 6.3 e.g) and remoting-http (for newer Wildfly AS).

      In the lib path "/usr/share/zabbix-java-gateway/lib" the jars are placed.

      android-json-4.3_r3.1.jar
      commons-logging-jboss-logmanager-1.0.2.Final-redhat-1.jar
      jboss-as-remoting-7.5.0.Final-redhat-21.jar
      jboss-cli-client.jar
      jboss-client.jar
      jboss-logging-3.1.4.GA-redhat-2.jar
      jboss-logging-3.3.1.Final-redhat-1.jar
      jboss-logmanager-1.5.4.Final-redhat-1.jar
      jboss-logmanager-2.0.7.Final-redhat-1.jar
      jboss-marshalling-1.4.10.Final-redhat-1.jar
      jboss-marshalling-2.0.2.Final-redhat-1.jar
      jboss-marshalling-river-1.4.10.Final-redhat-1.jar
      jboss-marshalling-river-2.0.2.Final-redhat-1.jar
      jboss-remoting-3.3.4.Final-redhat-1.jar
      jboss-remoting-5.0.5.Final-redhat-1.jar
      jboss-sasl-1.0.5.Final-redhat-1.jar
      jcl-over-slf4j-1.7.2.redhat-3.jar
      jul-to-slf4j-stub-1.0.1.Final-redhat-2.jar
      jul-to-slf4j-stub-1.0.1.Final-redhat-3.jar
      log4j-jboss-logmanager-1.1.1.Final-redhat-1.jar
      log4j-jboss-logmanager-1.1.4.Final-redhat-1.jar
      logback-classic-0.9.27.jar
      logback-core-0.9.27.jar
      remoting-jmx-1.1.3.Final-redhat-2.jar
      remoting-jmx-3.0.0.Final-redhat-1.jar
      slf4j-api-1.6.1.jar
      slf4j-api-1.7.22.redhat-1.jar
      slf4j-api-1.7.2.redhat-3.jar
      slf4j-jboss-logmanager-1.0.3.GA-redhat-2.jar
      xnio-api-3.0.13.GA-redhat-1.jar
      xnio-api-3.5.4.Final-redhat-1.jar
      xnio-nio-3.0.13.GA-redhat-1.jar
      xnio-nio-3.5.4.Final-redhat-1.jar
      

      There are connections from the Java Gateway which are refused, because the port is not open (JMX deactivated).
      Visible in Java-Gateway logfile: "java.net.ConnectException: Connection refused" which is more or less okay.

      There are a lot of error-messages in the zabbix-proxy.log.

      [root@proxyhostname]# grep <hostname>.*first /var/log/zabbix/zabbix_proxy.log | wc -l
       5376
      [root@proxyhostname]# grep <hostname>.*restored /var/log/zabbix/zabbix_proxy.log | wc -l
       5372
      

      Those were caused of a misconfigured item.

      Steps to reproduce:

      1. Don't know steps to reproduce.

      Result:
      See the screenshot of the graph which represents the memory-usage within the both proxy-machines. The dips are restarts of the zabbix-java-gateway. Dont know what happend when the usage rises extremely.

      Expected:
      Both zabbix-proxies are configured the same way.

      [root@proxy1]# grep -v '^$\|^#\|^TLS\|^Hostname' /etc/zabbix/zabbix_proxy.conf | md5sum
      5048f32c8a3b583f29a9c26270e8ac3d -
      [root@proxy2]# grep -v '^$\|^#\|^TLS\|^Hostname' /etc/zabbix/zabbix_proxy.conf | md5sum
      5048f32c8a3b583f29a9c26270e8ac3d -
      

      Both zabbix-java-gateways are configured the same way.

      Analysis is still ongoing here and I will give more informations if possible.

        1. zbx1.png
          104 kB
          Marcus Behrens
        2. zbx proxies mem heap.png
          147 kB
          Marcus Behrens

            zabbix.support Zabbix Support Team
            pagai Marcus Behrens
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: