[#ZBX-22204] Java gateway memory leak issues if old jboss-client.jar is used

2022-11-25 17:47:33.860 [Remoting "endpoint" I/O-1] ERROR org.xnio.listener - XNIO001007: A channel event listener threw an exception
java.util.concurrent.RejectedExecutionException: Task org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities$2@64e7ad27 rejected from org.xnio.XnioWorker$TaskPool@7bc20def[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]
        at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
        at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
        at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
        at org.xnio.XnioWorker.execute(XnioWorker.java:741)
        at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:454)
        at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
        at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
        at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:199)
        at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:113)
        at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
        at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1092)
        at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
        at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
        at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88)
        at org.xnio.nio.WorkerThread.run(WorkerThread.java:539)
java.lang.OutOfMemoryError: Java heap space
2022-11-25 18:24:35.193 [Thread-0] INFO  com.zabbix.gateway.JavaGateway - Zabbix Java Gateway 6.0.8 (revision c7c3044) has stopped
** Preparing Zabbix Java Gateway
** Preparing Zabbix Java Gateway log configuration file
Updating /etc/zabbix/zabbix_java_gateway_logback.xml 'DebugLevel' parameter: 'info'... updated

It occurs because of old jboss-client.jar is being used. Currently seems it only occurs if you try to monitor newer Wildfly versions.

The fix is quite simple - use the newest jboss-client.jar from the newest Wildfly release to run Zabbix Java gateway.

Can we please make a note on this in documentation? Something like this will suffice I believe:

If you are trying to monitor Wildfly based java applications with Zabbix Java Gateway, please install the latest jboss-client.jar available on the Wildfly download page. https://www.wildfly.org/downloads/

By default this jboss-client.jar should replace the existing one located here: /usr/share/zabbix-java-gateway/lib

[ZBX-22204] Java gateway memory leak issues if old jboss-client.jar is used Created: 2023 Jan 12 Updated: 2024 Apr 10 Resolved: 2023 Apr 24
Status:	Closed
Project:	ZABBIX BUGS AND ISSUES
Component/s:	Documentation (D), Java gateway (J)
Affects Version/s:	4.0.44, 5.0.30, 6.0.12, 6.2.6
Fix Version/s:	7.0 (plan)

[ZBX-22204] Java gateway memory leak issues if old jboss-client.jar is used Created: 2023 Jan 12 Updated: 2024 Apr 10 Resolved: 2023 Apr 24