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

trace level messages "timed out" in java gateway log file are not always related to time outs, so may mislead zabbix users. etc

XMLWordPrintable

      If enable TRACE level for logging (will be added to doc in (2) of ZBX-9824) we can see wrong messages:

      An 1.1.1.1 IP with successful check:

      2015-11-09 09:34:27.716 [pool-1-thread-2] DEBUG com.zabbix.gateway.SocketProcessor - starting to process incoming connection
2015-11-09 09:34:27.716 [pool-1-thread-2] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading Zabbix protocol header
2015-11-09 09:34:27.717 [pool-1-thread-2] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading 8 bytes of data length
2015-11-09 09:34:27.717 [pool-1-thread-2] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading 313 bytes of request data
2015-11-09 09:34:27.717 [pool-1-thread-2] DEBUG c.z.gateway.BinaryProtocolSpeaker - received the following data in request: {
	"request":"java gateway jmx",
	"conn":"1.1.1.1",
	"port":18080,
	"username":"admin",
	"password":"secure",
	"keys":["jmx[\"java.lang:type=GarbageCollector,name=PS MarkSweep\",\"CollectionTime\"]","jmx[\"java.lang:type=Memory\",\"HeapMemoryUsage.used\"]"]}
2015-11-09 09:34:27.717 [pool-1-thread-2] DEBUG com.zabbix.gateway.SocketProcessor - dispatched request to class com.zabbix.gateway.JMXItemChecker
2015-11-09 09:34:27.717 [pool-1-thread-2] DEBUG c.z.g.ZabbixJMXConnectorFactory - connecting to JMX agent at 'service:jmx:rmi:///jndi/rmi://1.1.1.1:18080/jmxrmi'
2015-11-09 09:34:27.717 [pool-2-thread-126] TRACE c.z.g.ZabbixJMXConnectorFactory - making a call to JMXConnectorFactory.connect('service:jmx:rmi:///jndi/rmi://1.1.1.1:18080/jmxrmi')
2015-11-09 09:34:28.826 [pool-2-thread-126] TRACE c.z.g.ZabbixJMXConnectorFactory - call to JMXConnectorFactory.connect('service:jmx:rmi:///jndi/rmi://1.1.1.1:18080/jmxrmi') successful
2015-11-09 09:34:28.826 [pool-1-thread-2] TRACE c.z.g.ZabbixJMXConnectorFactory - connector acquired
2015-11-09 09:34:28.827 [pool-1-thread-2] DEBUG com.zabbix.gateway.ItemChecker - getting value for item 'jmx["java.lang:type=GarbageCollector,name=PS MarkSweep","CollectionTime"]'
2015-11-09 09:34:28.827 [pool-1-thread-2] TRACE com.zabbix.gateway.JMXItemChecker - attributeName:'CollectionTime'
2015-11-09 09:34:28.827 [pool-1-thread-2] TRACE com.zabbix.gateway.JMXItemChecker - fieldNames:''
2015-11-09 09:34:28.854 [pool-1-thread-2] TRACE com.zabbix.gateway.JMXItemChecker - drilling down with data object '38238' and field names ''
2015-11-09 09:34:28.854 [pool-1-thread-2] DEBUG com.zabbix.gateway.ItemChecker - received value '38238' for item 'jmx["java.lang:type=GarbageCollector,name=PS MarkSweep","CollectionTime"]'
2015-11-09 09:34:28.854 [pool-1-thread-2] DEBUG com.zabbix.gateway.ItemChecker - getting value for item 'jmx["java.lang:type=Memory","HeapMemoryUsage.used"]'
2015-11-09 09:34:28.854 [pool-1-thread-2] TRACE com.zabbix.gateway.JMXItemChecker - 'HeapMemoryUsage.used' contains composite data
2015-11-09 09:34:28.855 [pool-1-thread-2] TRACE com.zabbix.gateway.JMXItemChecker - attributeName:'HeapMemoryUsage'
2015-11-09 09:34:28.855 [pool-1-thread-2] TRACE com.zabbix.gateway.JMXItemChecker - fieldNames:'used'
2015-11-09 09:34:28.882 [pool-1-thread-2] TRACE com.zabbix.gateway.JMXItemChecker - drilling down with data object 'javax.management.openmbean.CompositeDataSupport(compositeType=javax.management.openmbean.CompositeType(name=java.lang.management.MemoryUsage,items=((itemName=committed,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)),(itemName=init,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)),(itemName=max,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)),(itemName=used,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)))),contents={committed=2130903040, init=2147483648, max=2130903040, used=161326552})' and field names 'used'
2015-11-09 09:34:28.882 [pool-1-thread-2] TRACE com.zabbix.gateway.JMXItemChecker - 'javax.management.openmbean.CompositeDataSupport(compositeType=javax.management.openmbean.CompositeType(name=java.lang.management.MemoryUsage,items=((itemName=committed,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)),(itemName=init,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)),(itemName=max,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)),(itemName=used,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)))),contents={committed=2130903040, init=2147483648, max=2130903040, used=161326552})' contains composite data
2015-11-09 09:34:28.882 [pool-1-thread-2] TRACE com.zabbix.gateway.JMXItemChecker - drilling down with data object '161326552' and field names ''
2015-11-09 09:34:28.883 [pool-1-thread-2] DEBUG com.zabbix.gateway.ItemChecker - received value '161326552' for item 'jmx["java.lang:type=Memory","HeapMemoryUsage.used"]'
2015-11-09 09:34:28.915 [pool-1-thread-1] DEBUG com.zabbix.gateway.SocketProcessor - starting to process incoming connection
2015-11-09 09:34:28.915 [pool-1-thread-1] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading Zabbix protocol header
2015-11-09 09:34:28.919 [pool-1-thread-2] DEBUG c.z.gateway.BinaryProtocolSpeaker - sending the following data in response: {"response":"success","data":[{"value":"38238"},{"value":"161326552"}]}
2015-11-09 09:34:28.920 [pool-1-thread-2] DEBUG com.zabbix.gateway.SocketProcessor - finished processing incoming connection

      The trace message "timed out" is misleading, as it can be seen in other cases too, which are not time outs.

      Credentials required case:

      2015-11-09 09:33:28.066 [pool-1-thread-2] DEBUG com.zabbix.gateway.SocketProcessor - starting to process incoming connection
2015-11-09 09:33:28.067 [pool-1-thread-2] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading Zabbix protocol header
2015-11-09 09:33:28.067 [pool-1-thread-2] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading 8 bytes of data length
2015-11-09 09:33:28.067 [pool-1-thread-2] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading 140 bytes of request data
2015-11-09 09:33:28.067 [pool-1-thread-2] DEBUG c.z.gateway.BinaryProtocolSpeaker - received the following data in request: {
	"request":"java gateway jmx",
	"conn":"2.2.2.2",
	"port":18080,
	"keys":["jmx[\"java.lang:type=Memory\",\"HeapMemoryUsage.used\"]"]}
2015-11-09 09:33:28.067 [pool-1-thread-2] DEBUG com.zabbix.gateway.SocketProcessor - dispatched request to class com.zabbix.gateway.JMXItemChecker
2015-11-09 09:33:28.067 [pool-1-thread-2] DEBUG c.z.g.ZabbixJMXConnectorFactory - connecting to JMX agent at 'service:jmx:rmi:///jndi/rmi://2.2.2.2:18080/jmxrmi'
2015-11-09 09:33:28.067 [pool-2-thread-126] TRACE c.z.g.ZabbixJMXConnectorFactory - making a call to JMXConnectorFactory.connect('service:jmx:rmi:///jndi/rmi://2.2.2.2:18080/jmxrmi')
2015-11-09 09:33:28.083 [pool-2-thread-126] TRACE c.z.g.ZabbixJMXConnectorFactory - call to JMXConnectorFactory.connect('service:jmx:rmi:///jndi/rmi://2.2.2.2:18080/jmxrmi') timed out
2015-11-09 09:33:28.084 [pool-1-thread-2] TRACE c.z.g.ZabbixJMXConnectorFactory - connector acquired
2015-11-09 09:33:28.085 [pool-1-thread-2] WARN  com.zabbix.gateway.SocketProcessor - error processing request
com.zabbix.gateway.ZabbixException: java.lang.SecurityException: Authentication failed! Credentials required
	at com.zabbix.gateway.JMXItemChecker.getValues(JMXItemChecker.java:97) ~[zabbix-java-gateway-2.4.6.jar:na]
	at com.zabbix.gateway.SocketProcessor.run(SocketProcessor.java:63) ~[zabbix-java-gateway-2.4.6.jar:na]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_85]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_85]
	at java.lang.Thread.run(Thread.java:745) [na:1.7.0_85]
Caused by: java.lang.SecurityException: Authentication failed! Credentials required
	at com.sun.jmx.remote.security.JMXPluggableAuthenticator.authenticationFailure(JMXPluggableAuthenticator.java:211) ~[na:1.7.0_85]
	at com.sun.jmx.remote.security.JMXPluggableAuthenticator.authenticate(JMXPluggableAuthenticator.java:163) ~[na:1.7.0_85]
	at javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:232) ~[na:1.7.0_85]
	at javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:199) ~[na:1.7.0_85]
	at sun.reflect.GeneratedMethodAccessor177.invoke(Unknown Source) ~[na:na]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_85]
	at java.lang.reflect.Method.invoke(Method.java:601) ~[na:1.7.0_85]
	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322) ~[na:1.7.0_85]
	at sun.rmi.transport.Transport$1.run(Transport.java:177) ~[na:1.7.0_85]
	at sun.rmi.transport.Transport$1.run(Transport.java:174) ~[na:1.7.0_85]
	at java.security.AccessController.doPrivileged(Native Method) ~[na:1.7.0_85]
	at sun.rmi.transport.Transport.serviceCall(Transport.java:173) ~[na:1.7.0_85]
	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:553) ~[na:1.7.0_85]
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:808) ~[na:1.7.0_85]
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:667) ~[na:1.7.0_85]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_85]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_85]
	at java.lang.Thread.run(Thread.java:722) [na:1.7.0_85]
	at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:275) ~[na:1.7.0_85]
	at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:252) ~[na:1.7.0_85]
	at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161) ~[na:1.7.0_85]
	at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source) ~[na:1.7.0_85]
	at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2404) ~[na:1.7.0_85]
	at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:308) ~[na:1.7.0_85]
	at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:268) ~[na:1.7.0_85]
	at com.zabbix.gateway.ZabbixJMXConnectorFactory$1.run(ZabbixJMXConnectorFactory.java:76) ~[zabbix-java-gateway-2.4.6.jar:na]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) ~[na:1.7.0_85]
	at java.util.concurrent.FutureTask.run(FutureTask.java:262) ~[na:1.7.0_85]
	... 3 common frames omitted
2015-11-09 09:33:28.086 [pool-1-thread-2] DEBUG c.z.gateway.BinaryProtocolSpeaker - sending the following data in response: {"response":"failed","error":"java.lang.SecurityException: Authentication failed! Credentials required"}
2015-11-09 09:33:28.087 [pool-1-thread-2] DEBUG com.zabbix.gateway.SocketProcessor - finished processing incoming connection

      Connection refused by ICMP case:

      2015-11-09 09:33:10.067 [pool-1-thread-4] DEBUG com.zabbix.gateway.SocketProcessor - starting to process incoming connection
2015-11-09 09:33:10.067 [pool-1-thread-4] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading Zabbix protocol header
2015-11-09 09:33:10.067 [pool-1-thread-4] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading 8 bytes of data length
2015-11-09 09:33:10.067 [pool-1-thread-4] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading 253 bytes of request data
2015-11-09 09:33:10.067 [pool-1-thread-4] DEBUG c.z.gateway.BinaryProtocolSpeaker - received the following data in request: {
	"request":"java gateway jmx",
	"conn":"3.3.3.3",
	"port":18080,
	"username":"admin",
	"password":"secure",
	"keys":["jmx[\"java.lang:type=GarbageCollector,name=PS MarkSweep\",\"CollectionTime\"]"]}
2015-11-09 09:33:10.067 [pool-1-thread-4] DEBUG com.zabbix.gateway.SocketProcessor - dispatched request to class com.zabbix.gateway.JMXItemChecker
2015-11-09 09:33:10.068 [pool-1-thread-4] DEBUG c.z.g.ZabbixJMXConnectorFactory - connecting to JMX agent at 'service:jmx:rmi:///jndi/rmi://3.3.3.3:18080/jmxrmi'
2015-11-09 09:33:10.068 [pool-2-thread-126] TRACE c.z.g.ZabbixJMXConnectorFactory - making a call to JMXConnectorFactory.connect('service:jmx:rmi:///jndi/rmi://3.3.3.3:18080/jmxrmi')
2015-11-09 09:33:10.070 [pool-2-thread-126] TRACE c.z.g.ZabbixJMXConnectorFactory - call to JMXConnectorFactory.connect('service:jmx:rmi:///jndi/rmi://3.3.3.3:18080/jmxrmi') timed out
2015-11-09 09:33:10.071 [pool-1-thread-4] TRACE c.z.g.ZabbixJMXConnectorFactory - connector acquired
2015-11-09 09:33:10.076 [pool-1-thread-4] WARN  com.zabbix.gateway.SocketProcessor - error processing request
com.zabbix.gateway.ZabbixException: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 3.3.3.3; nested exception is: 
	java.net.ConnectException: Connection refused]
	at com.zabbix.gateway.JMXItemChecker.getValues(JMXItemChecker.java:97) ~[zabbix-java-gateway-2.4.6.jar:na]
	at com.zabbix.gateway.SocketProcessor.run(SocketProcessor.java:63) ~[zabbix-java-gateway-2.4.6.jar:na]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_85]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_85]
	at java.lang.Thread.run(Thread.java:745) [na:1.7.0_85]
Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 3.3.3.3; nested exception is: 
	java.net.ConnectException: Connection refused]
	at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:369) ~[na:1.7.0_85]
	at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:268) ~[na:1.7.0_85]
	at com.zabbix.gateway.ZabbixJMXConnectorFactory$1.run(ZabbixJMXConnectorFactory.java:76) ~[zabbix-java-gateway-2.4.6.jar:na]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) ~[na:1.7.0_85]
	at java.util.concurrent.FutureTask.run(FutureTask.java:262) ~[na:1.7.0_85]
	... 3 common frames omitted
Caused by: javax.naming.ServiceUnavailableException: null
	at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:118) ~[na:1.7.0_85]
	at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:203) ~[na:1.7.0_85]
	at javax.naming.InitialContext.lookup(InitialContext.java:411) ~[na:1.7.0_85]
	at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1929) ~[na:1.7.0_85]
	at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1896) ~[na:1.7.0_85]
	at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:286) ~[na:1.7.0_85]
	... 7 common frames omitted
Caused by: java.rmi.ConnectException: Connection refused to host: 3.3.3.3; nested exception is: 
	java.net.ConnectException: Connection refused
	at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619) ~[na:1.7.0_85]
	at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216) ~[na:1.7.0_85]
	at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202) ~[na:1.7.0_85]
	at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:341) ~[na:1.7.0_85]
	at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source) ~[na:1.7.0_85]
	at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:114) ~[na:1.7.0_85]
	... 12 common frames omitted
Caused by: java.net.ConnectException: Connection refused
	at java.net.PlainSocketImpl.socketConnect(Native Method) ~[na:1.7.0_85]
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) ~[na:1.7.0_85]
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) ~[na:1.7.0_85]
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) ~[na:1.7.0_85]
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[na:1.7.0_85]
	at java.net.Socket.connect(Socket.java:579) ~[na:1.7.0_85]
	at java.net.Socket.connect(Socket.java:528) ~[na:1.7.0_85]
	at java.net.Socket.<init>(Socket.java:425) ~[na:1.7.0_85]
	at java.net.Socket.<init>(Socket.java:208) ~[na:1.7.0_85]
	at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40) ~[na:1.7.0_85]
	at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:147) ~[na:1.7.0_85]
	at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613) ~[na:1.7.0_85]
	... 17 common frames omitted
2015-11-09 09:33:10.076 [pool-1-thread-4] DEBUG c.z.gateway.BinaryProtocolSpeaker - sending the following data in response: {"response":"failed","error":"java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 3.3.3.3; nested exception is: \n\tjava.net.ConnectException: Connection refused]"}
2015-11-09 09:33:10.077 [pool-1-thread-4] DEBUG com.zabbix.gateway.SocketProcessor - finished processing incoming connection

      I believe is as a bug.

      (1) The "timed out" should be replaced to just "unsuccessful"
      (2) and I suppose then message "connector acquired" should not be logged in such cases.

      Example of a real timeout, just in case:

      2015-12-03 15:43:19.567 [pool-1-thread-1] DEBUG com.zabbix.gateway.SocketProcessor - starting to process incoming connection
2015-12-03 15:43:19.571 [pool-1-thread-1] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading Zabbix protocol header
2015-12-03 15:43:19.571 [pool-1-thread-1] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading 8 bytes of data length
2015-12-03 15:43:19.571 [pool-1-thread-1] DEBUG c.z.gateway.BinaryProtocolSpeaker - reading 233 bytes of request data
2015-12-03 15:43:19.572 [pool-1-thread-1] DEBUG c.z.gateway.BinaryProtocolSpeaker - received the following data in request: {
        "request":"java gateway jmx",
        "conn":"123.123.123.123",
        "port":12345,
        "username":"username",
        "password":"password",
        "keys":["jmx[\"java.lang:type=Memory\",\"HeapMemoryUsage.used\"]"]}
2015-12-03 15:43:19.582 [pool-1-thread-1] DEBUG com.zabbix.gateway.SocketProcessor - dispatched request to class com.zabbix.gateway.JMXItemChecker
2015-12-03 15:43:19.583 [pool-1-thread-1] DEBUG c.z.g.ZabbixJMXConnectorFactory - connecting to JMX agent at 'service:jmx:rmi:///jndi/rmi://123.123.123.123:12345/jmxrmi'
2015-12-03 15:43:19.585 [pool-2-thread-1] TRACE c.z.g.ZabbixJMXConnectorFactory - making a call to JMXConnectorFactory.connect('service:jmx:rmi:///jndi/rmi://123.123.123.123:12345/jmxrmi')
2015-12-03 15:43:22.585 [pool-1-thread-1] TRACE c.z.g.ZabbixJMXConnectorFactory - no connector after 3 seconds
2015-12-03 15:43:22.598 [pool-1-thread-1] WARN  com.zabbix.gateway.SocketProcessor - error processing request
com.zabbix.gateway.ZabbixException: java.net.SocketTimeoutException: connection timed out: service:jmx:rmi:///jndi/rmi://123.123.123.123:12345/jmxrmi
	at com.zabbix.gateway.JMXItemChecker.getValues(JMXItemChecker.java:97) ~[zabbix-java-gateway.jar:na]
	at com.zabbix.gateway.SocketProcessor.run(SocketProcessor.java:63) ~[zabbix-java-gateway.jar:na]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_85]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_85]
	at java.lang.Thread.run(Thread.java:745) [na:1.7.0_85]
Caused by: java.net.SocketTimeoutException: connection timed out: service:jmx:rmi:///jndi/rmi://123.123.123.123:12345/jmxrmi
	at com.zabbix.gateway.ZabbixJMXConnectorFactory.connect(ZabbixJMXConnectorFactory.java:123) ~[zabbix-java-gateway.jar:na]
	at com.zabbix.gateway.JMXItemChecker.getValues(JMXItemChecker.java:89) ~[zabbix-java-gateway.jar:na]
	... 4 common frames omitted
2015-12-03 15:43:22.604 [pool-1-thread-1] DEBUG c.z.gateway.BinaryProtocolSpeaker - sending the following data in response: {"response":"failed","error":"java.net.SocketTimeoutException: connection timed out: service:jmx:rmi:\/\/\/jndi\/rmi:\/\/123.123.123.123:12345\/jmxrmi"}
2015-12-03 15:43:22.605 [pool-1-thread-1] DEBUG com.zabbix.gateway.SocketProcessor - finished processing incoming connection

            Unassigned Unassigned
            zalex_ua Oleksii Zagorskyi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: