1 title: Memory usage of Java application server via JMX and j4p.war - DEPRECATED
7 Do not use this plugin. It will be removed soon. Use jolokia_metrics instead.
9 This checks uses the JSON HTTP service of j4p (from jmx4perl) to
10 monitor the current memory usage of a Java application server like
11 Tomcat or JBoss. You can define levels against the total memory
12 usage of the Java machine (heap + non heap).
14 In order for the check to work, you need to load the j4p.war into your
15 application server. Furthermore you need the agent plugin {j4p_performance}
16 in your Check_MK agent's plugins directory. If you do not use the
17 default port 8080 for j4p - lets say {9090} - then you have to create
18 a configuration file {j4p.conf} in the agents configuration directory
19 (usually {/etc/check_mk/j4p.conf}) with the single line {port = 9090}.
21 Note: No jmx4perl is needed - neither on the target host nor
22 on the monitoring server. No Perl is needed, either.
23 The agent connects to the application server always via {localhost}.
26 The instance name as configured in {j4p.conf} with the variable
27 {instance}. If you do not specify an instance then the port number
28 converted to a string is used.
30 Please note that the current implementation of the agent plugin
31 supports only one instance per host.
34 One check is created for each JMX instance sent by the agent.
35 The agent currently supports only one instance, but that might