[javamelody] HTTP monitoring and javamelody

[dhartford]

Hi all,
I have an http monitor running on one of my projects that is deployed
with javamelody.

This combination seems to provide slightly undesirable information in
javamelody - like +30 more HTTP Session counts as the http monitor
checks it frequently (every 5 min).

Can anyone provide any hints to work around, or with, http
monitoring?

--I want to keep HTTP monitoring, and keep it monitoring a 'regular'
application page.
--Filtering the http session count based on the monitoring IP address
is my first thought -- but at that point the http session details/ejb
details become distorted compared to the count.
--the 'full' http session count is still important (even with the http
monitoring) to manage and configure the max active sessions for your
tomcat/jboss/etc.

My initial hunch would be for the graph to keep the blue line/maxline
where it is, but reduce the regular session graph values to not
include a filtered IP address (like the http monitor).

Going beyond that into the http session details/ejb-details may get a
bit trickier however, but considering how useful Javamelody already is
as-is, just changing the above 'high level graph' to reflect what is
user-sessions versus http monitoring (IP Filtered) sessions should be
enough.

thoughts?

-D

[Emeric Vernat]

Hi D.

I would try that your external HTTP monitor does not open an http
session in your application, or otherwise that the HTTP monitor closes
the http session after opening it.
For example, if your HTTP monitor can call several URL in a test and if
it can read the session cookie sent by the server, make it call a
"logout" URL as the last one.
Or if it can't, add in your server something like
"httpRequest.getSession().close()" at the end of the http request when
it is the HTTP monitor (based on the URL, or a parameter or
httpRequest.getRemoteAddr() or ...)

If someone has other thoughts...

bye, Emeric


Le 24/05/2010 13:46, dhartford a �crit :