zabbix-java-gateway(1)

💖 zabbix-java-gateway(1) 💖

okay bestie, pull up a chair, we're reading the manual page for zabbix-java-gateway(1) and honestly? it's giving main character energy. ✨

---

🌸 NAME 🌸

zabbix-java-gateway.jar — the Zabbix Java/JMX monitoring agent. yes she's a whole daemon and yes she's iconic for it 💅

---

🎀 USAGE 🎀

/etc/init.d/zabbix-java-gateway [ start|stop|restart|status ]

that's it, that's the whole vibe. four little verbs and she's running your life 🫶

---

✨ DESCRIPTION ✨

okay so. "Zabbix Java gateway" is a daemon whose whole job is collecting information from a JMX agent. 🧚

here's the tea: when the Zabbix server is like "bestie what's the value of this particular JMX counter on this host 👀", it asks the Zabbix Java gateway, and the gateway uses the JMX management API to go query the application of interest remotely. and the best part?? the application needs zero additional software installed. nothing. nada. it just has to be started with the -Dcom.sun.management.jmxremote option to Java on the command line. that's the whole requirement. we love a low-maintenance queen. 👑

Java gateway accepts incoming connections from Zabbix server or proxy and can only be used as a "passive proxy". now, as opposed to Zabbix proxy, it may also be used from Zabbix proxy — because (and this is important, don't @ me) Zabbix proxies cannot be chained. 🚫

access to each Java gateway is configured directly in the Zabbix server or proxy configuration file, which means only one Java gateway may be configured per Zabbix server or Zabbix proxy. one. singular. monogamous. 💜

and if a host has items of type JMX agent and items of other type? only the JMX agent items will be passed to Java gateway for retrieval. the rest get left on read. 🙈

when an item has to be updated over Java gateway, Zabbix server or proxy will connect to the Java gateway and request the value, which Java gateway in turn retrieves and passes back to the server or proxy. and as such — say it with me — Java gateway does not cache any values. no hoarding, no saving things for later, she's present in the moment, mindfulness queen 🧘

Zabbix server or proxy has a specific type of processes that connect to Java gateway, controlled by the option "StartJavaPollers". internally, Java gateway starts multiple threads, controlled by the START_POLLERS option. now on the server side, if a connection takes more than Timeout seconds, it will be terminated — but plot twist 😭 — Java gateway might still be busy retrieving the value from the JMX counter. she's still working, the connection just left the group chat.

Zabbix server or proxy will try to pool requests to a single JMX target together as much as possible (this is affected by item intervals, fyi) and send them to the Java Gateway in a single connection for better performance. efficiency era. 🔥

and here's the advice you actually need: it is suggested to have "StartJavaPollers" less than or equal to START_POLLERS. otherwise there might be situations when no threads are available in the Java gateway to service incoming requests. and nobody wants that. it's giving overwhelmed. 💀

---

⭐ OPTIONS ⭐

• -V, --version — display version number. short, sweet, slays.

---

🌈 JAVA OPTIONS 🌈

zabbix-java-gateway.jar recognises the following Java options:

• -Dzabbix.pidFile
• -Dlogback.configurationFile — example: -Dlogback.configurationFile=/etc/zabbix/logback.xml
• -Dzabbix.listenIP
• -Dzabbix.listenPort
• -Dzabbix.startPollers

---

🦋 CONFIGURATION FILES 🦋

• /etc/zabbix/logback.xml — logging configuration.
• /etc/zabbix/zabbix_java_gateway.conf — miscellaneous parameters.

---

👑 SEE ALSO 👑

• <https://www.zabbix.com/documentation/5.0/manual/config/items/itemtypes/jmx_monitoring>
• <https://www.zabbix.com/documentation/5.0/manual/concepts/java>

---

and that's the page, bestie 💖 this one's zabbix 2.2.0, dated November 2013 — so yeah, she's been serving since 2013 and she has not missed a day. periodt. 🎀✨🫶