Zapcat 1.3 released, adds templates for Java, Hibernate and Tomcat servlet containers

[Kees Jan Koster]

Good to see that ou already have jconsole working and that the Zapcat agent is up and running. The next step is to check your host configuration in Zabbix. Check that Zabbix is configured to connect to the right IP address and port number.

If that configuration is correct, telnet to the Zapcat agent as discussed in this post.

Do you get any error messages in the Zabbix server logs or in the Zabbix UI?

[OneLoveAmaru]

Yes, I get this in the zabbix server logs:

5284:20080706:140437 Parameter [jmx[Catalina:type=GlobalRequestProcessor,name=http-8080][requestCount]] is not supported by agent on host [Crash - Tom
cat] Old status [0]
5284:20080706:140437 Parameter [jmx[Catalina:type=ThreadPool,name=http-8443][currentThreadCount]] is not supported by agent on host [Crash - Tomcat] O
ld status [0]
5284:20080706:140437 Parameter [jmx[Catalina:type=GlobalRequestProcessor,name=http-8443][requestCount]] is not supported by agent on host [Crash - Tom
cat] Old status [0]
5284:20080706:140437 Expression [{17767}>({17766}*0.7)] cannot be evaluated [Unable to get value for functionid [17767]]
5286:20080706:140437 Parameter [jmx[Catalina:type=GlobalRequestProcessor,name=http-8443][bytesSent]] is not supported by agent on host [Crash - Tomcat
] Old status [0]
5286:20080706:140438 Parameter [jmx[Catalina:type=ThreadPool,name=http-8443][maxThreads]] is not supported by agent on host [Crash - Tomcat] Old statu
s [0]
5286:20080706:140438 Parameter [jmx[Catalina:type=Manager,path=/,host=localhost][maxActiveSessions]] is not supported by agent on host [Crash - Tomcat
] Old status [0]
5286:20080706:140438 Parameter [jmx[Catalina:type=GlobalRequestProcessor,name=http-8080][bytesSent]] is not supported by agent on host [Crash - Tomcat
] Old status [0]
5286:20080706:140438 Parameter [jmx[Catalina:type=ThreadPool,name=http-8080][currentThreadCount]] is not supported by agent on host [Crash - Tomcat] O
ld status [0]
5285:20080706:140439 Parameter [jmx[Catalina:type=GlobalRequestProcessor,name=http-8443][bytesReceived]] is not supported by agent on host [Crash - To
mcat] Old status [0]
5285:20080706:140439 Parameter [jmx[Catalina:type=ThreadPool,name=http-8443][currentThreadsBusy]] is not supported by agent on host [Crash - Tomcat] O
ld status [0]
5285:20080706:140439 Parameter [jmx[Catalina:type=Manager,path=/,host=localhost][activeSessions]] is not supported by agent on host [Crash - Tomcat] O
ld status [0]
5285:20080706:140439 Parameter [jmx[Catalina:type=GlobalRequestProcessor,name=http-8080][bytesReceived]] is not supported by agent on host [Crash - To
mcat] Old status [0]
5282:20080706:140439 Parameter [jmx[Catalina:type=GlobalRequestProcessor,name=http-8443][errorCount]] is not supported by agent on host [Crash - Tomca
t] Old status [0]
5282:20080706:140439 Parameter [jmx[Catalina:type=Manager,path=/,host=localhost][rejectedSessions]] is not supported by agent on host [Crash - Tomcat]
Old status [0]
5282:20080706:140439 Parameter [jmx[Catalina:type=GlobalRequestProcessor,name=http-8080][errorCount]] is not supported by agent on host [Crash - Tomca
t] Old status [0]
5282:20080706:140439 Parameter [jmx[Catalina:type=ThreadPool,name=http-8080][currentThreadsBusy]] is not supported by agent on host [Crash - Tomcat] O
ld status [0]
5283:20080706:140439 Parameter [jmx[Catalina:type=GlobalRequestProcessor,name=http-8443][processingTime]] is not supported by agent on host [Crash - T
omcat] Old status [0]
5283:20080706:140439 Parameter [jmx[Catalina:type=ProtocolHandler,port=8080][compression]] is not supported by agent on host [Crash - Tomcat] Old stat
us [0]
5283:20080706:140439 Parameter [jmx[Catalina:type=GlobalRequestProcessor,name=http-8080][processingTime]] is not supported by agent on host [Crash - T
omcat] Old status [0]
5283:20080706:140439 Parameter [jmx[Catalina:type=ThreadPool,name=http-8080][maxThreads]] is not supported by agent on host [Crash - Tomcat] Old statu
s [0]


and this is what it shows me in the web ui.




Any suggestions?? Server is 1.4.5, agent is 1.4.4.

[Kees Jan Koster]

Ahh, I see the problem now. Zapcat actually works fine. ;-)

If you check the screenshot you see that some items work as expected. The JK connector for example. These are marked as "Active" and shown in green. That shows that the Zapcat agent is operating normally.

Most likely, you have disabled the HTTP ports on this Tomcat, or moved them to different port numbers than the ones in the Tomcat template.

If you open the JSP page in the WAR file, you will see a link that allows you to generate a custom template, specifically for your Tomcat configuration. This is discussed on the Zapcat Tomcat howto page under the heading "Tomcat Template and Host Definition".

Please let me know if it worked.

[OneLoveAmaru]

You are the man. I'm still getting some errors though and when I go to Monitoring/Overview, only 2 items from the template are green and one is yellow. You can see the errors from the picture below and you can visit my site and see what's showing and what's not. The host is named "Corp - Crash - Tomcat" that zapcat is running on.

http://zabbix.corp.newhomes.com/zabbix/overview.php

[Kees Jan Koster]

Dear OneLoveAmaru,

I took the liberty to have a look around in your Zabbix server. Everything Tomcat related looks fine. The errors you posted (aside: an interesting spelling of the word 'suitable') are odd. It seems you are running with the max active sessions for each context uncapped.

There seems to be a type mismatch between the Zabbix integer type and the Java integer type.

*flick, flick*

Ahh. The Zabbix manual says that integers in Zabbix are 64-bit unsigned integers. Good catch. Hmm. I have to think about that one for a bit.

You could make the items into float items instead of int. That should allow you to receive the item's value properly ... if that's worth the trouble.

Kees Jan

[OneLoveAmaru]

I can deal without those. I am getting a lot of information now and if tomcat hiccups, I'm sure I'll be alerted. I'm also going to get an apache trigger going and also a http status, like 200, 400, 500 errors. The main goal is to know when apache, tomcat hiccup and when our site goes down because of this. Thanks for all of your help. Any Debian or Ubuntu user searching out there, that wants this info should stumble upon this site and get enough info to get it up and running.

Thanks again bro. If I have any more questions I'll be back.

[Kees Jan Koster]

No problem. Glad you find Zapcat useful. Be sure to post here when you got a hiccup and solved it. We can all learn from that.

[bignose]

I have an app that latley has been consuming the entire heap then killing jboss..

Does anyone have the object and property name for JMX so I can monitor my heap usage? The templates didn't include this in it, PermGen sure, but not heap.

Thanks...

[sybex]

Hi, ...

i made a small bash script to get these values from the JBoss status page because zapcat delivers no data anymore since 1.8.3 correctly.

This ist not the non plus ultra way ... but it works for me.
You have to add the items in zabbix to an template or to the hosts.
Can be used for more than one jboss server ...

It is directly running on my zabbix server.

#!/bin/bash

INPUT=/tmp/jboss_input.xml
OUTPUT=/tmp/jboss_output.txt
HOSTS="HOST1 HOST2"
ZABBIX=/usr/local/bin/zabbix_sender

for server in $HOSTS
do

  wget -q -O - http://$server:8080/status?XML=true > $INPUT

  xmllint $INPUT --shell <<EOF>$OUTPUT
    cd status
    cat
    bye
EOF

  MAX=$(grep memory $OUTPUT | awk '{print $4}' | sed 's/max\="//' | sed 's/"\/>//')
  FREE=$(grep memory $OUTPUT | awk '{print $2}' | sed 's/free="//' | sed 's/\"//')
  ALOC=$(grep memory $OUTPUT | awk '{print $3}' | sed 's/total="//' | sed 's/\"//')
  let "USE= $ALOC-$FREE"

  if [ $server = "HOST1" ]; then NAME=<zabbixservername_host1>; fi
  if [ $server = "HOST2" ]; then NAME=<zabbixservername_host2>; fi

  $ZABBIX -z localhost -s "$NAME" -k "jboss.mem.max" -o "$MAX"
  $ZABBIX -z localhost -s "$NAME" -k "jboss.mem.use" -o "$USE"
  $ZABBIX -z localhost -s "$NAME" -k "jboss.mem.aloc" -o "$ALOC"

done

rm -f $INPUT $OUTPUT

exit