Zabbix Documentation 4.2

3.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.22.43.23.4

User Tools

Site Tools


manual:concepts:java

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
manual:concepts:java [2019/05/15 05:11]
martins-v Java gateway uses ThreadPoolExecutor.CallerRunsPolicy with no threads available
manual:concepts:java [2019/05/15 05:11] (current)
martins-v punctuation fix
Line 13: Line 13:
 Zabbix server or proxy will try to pool requests to a single JMX target together as much as possible (affected by item intervals) and send them to the Java gateway in a single connection for better performance. Zabbix server or proxy will try to pool requests to a single JMX target together as much as possible (affected by item intervals) and send them to the Java gateway in a single connection for better performance.
  
-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; in such a case Java gateway uses ThreadPoolExecutor.CallerRunsPolicy,​ meaning that the main thread will service the incoming request and temporarily will not accept any new requests..+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; in such a case Java gateway uses ThreadPoolExecutor.CallerRunsPolicy,​ meaning that the main thread will service the incoming request and temporarily will not accept any new requests.
  
 === Getting Java gateway === === Getting Java gateway ===