There are plenty of helpful tools to test network services. If you want to check HTTP functionality, you could craft a request with curl, wget or “siege -g” to see if a server is functioning. If you understand the service protocol, you can always telnet to a TCP port and type a transaction.
Unfortunately, there aren’t many tools to help you test AJP protocol. Sure, you can telnet to the port to ensure it’s running, but how many people know how to craft an AJP transaction? I didn’t.
In order to help you test AJP servers like Apache’s tomcat, I wrote ajping. It connects to a user-define port and conducts a simple transaction. ajping validates the server’s response and clocks the length of the transaction. Over the LAN, you should expect times in the hundreds of seconds. This is a command line utility. In order to install it, run the following commands:
$ wget http://download.joedog.org/AJP/ajping.txt $ mv ajping.txt ajping $ chmod +x ajping
You can test a server with it like this:
LT $ ajping tommy.joedog.org:8009 Reply from tommy.joedog.org: 7 bytes in 0.019 seconds Reply from tommy.joedog.org: 7 bytes in 0.004 seconds Reply from tommy.joedog.org: 7 bytes in 0.004 seconds Reply from tommy.joedog.org: 7 bytes in 0.011 seconds Reply from tommy.joedog.org: 7 bytes in 0.004 seconds Reply from tommy.joedog.org: 7 bytes in 0.016 seconds Reply from tommy.joedog.org: 7 bytes in 0.009 seconds Reply from tommy.joedog.org: 7 bytes in 0.021 seconds Reply from tommy.joedog.org: 7 bytes in 0.011 seconds Reply from tommy.joedog.org: 7 bytes in 0.025 seconds
I’ve also incorporated this code into a check_ajp script for Zenoss. Remove the .txt extension and install it on Zenoss as you would any other script. Happy hacking.
UPDATE: I fixed the links to point to the new download location. H/T paalfe