Added by Ard Schrijvers, last edited by Jeroen Reijn on Oct 07, 2008  (view change)

Labels:

tcpmon tcpmon Delete
webdav webdav Delete
performance performance Delete
tuning tuning Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

tcpmon is used to monitor the data flowing on a TCP connection. tcpmon is used by placing it in-between a client and a server. The client is made to connect to tcpmon, and tcpmon forwards the data to server along-with displaying it in its GUI.

We use tcpmon for testing if repository sources are cached properly: Instead of connecting the site to the repository on a specific port, we connect to localhost on a port tcpmon listens to. Tcpmon forwards the request to the repository server. If sources are cached well, then after the first hit, NO tcpmon data transfer must be visible when refreshing the page!

You can find it here:
https://tcpmon.dev.java.net/

A sample test script for the CMS is available on the hippocms-dev mailing list: http://lists.hippo.nl/pipermail/hippocms-dev/2007-October/003771.html

Setting up TCP Mon!

Configuring TCP Mon

Adding the monitor

Press 'Add monitor' to add the current monitor to TCPMon.

Sending a requesting through

Now open up a browser and request for the page 'http://localhost:60001/default/files'.

Looking at the result

Once the request is finished, you should see it in the result pane of TCP Mon. At the top you will see the request and at the bottom you will see the response.