Dynamic import 5.1.4. OSGi framework 5.1.5. Stack traces printout 5.1.6. Bundle tree 5.1.7. Watch 5.2. Scripting 5.2.1. Assignation 5.2.2. Expressions 5.2.3. List, maps, pipes and closures 5.2.4. Startup │ true │ false │ 1 zabbix/zabbix-java-gateway │ Zabbix Java Gateway │ true │ false │ 13 jetty It’s not always easy to use a JMX client with the RMI protocol. Some monitoring tools (Nagios, Zabbix, …) are not native JMX clients. But most of them can use HTTP. More over, you may want to write

4.1. Hazelcast cluster identification 4.2. Network 5. Cellar nodes 5.1. Nodes identification 5.2. Testing nodes 5.3. Node Components: listener, producer, handler, consume, and synchronizer 5.4. configuration is multicast enabled, tcp-ip disabled. See [Core Configuration|hazelcast] for details. 5.2. Testing nodes You can ping a node to test it: 5.3. Node Components: listener, producer, handler

4.1. Hazelcast cluster identification 4.2. Network 5. Cellar nodes 5.1. Nodes identification 5.2. Testing nodes 5.3. Node Components: listener, producer, handler, consume, and synchronizer 5.4. configuration is multicast enabled, tcp-ip disabled. See Core Configuration section for details. 5.2. Testing nodes You can ping a node to test it: 5.3. Node Components: listener, producer, handler