We are running a few tomcat servers. One of those servers runs a number of identical "/webapps".
We are using lambda probe to monitor those /webapps.
Two of those "/webapps" are running crazy on the displayed "sessions" count. (read: 1000 to 10000 sessions for max 50 unique visitors according to Google Analytics.)
Other (identical) apps (on the same server) behave normally.
Right now we are looking for (a) the reason for this or (b) a different way of counting the currently active sessions.
Any ideas, guesses, or pointers that could help us?
(None of us does any java coding. We administer that machine, though. I didn't develop any of the applications running on those servers. Session timeout is 30mins. 3 tomcats are on different ports of the same machine. No connectors involved.)
Joined: Nov 20, 2009
I refined my probe'ing ...
1) There is always a number of "private" IPs (they don't look like crawler-bots), which open more than a dozen sessions each. Resulting in a lot of sessions per IP.
2) One new session for the same IP per minute, roughly. (therefore I don't think a single browser is opening that many sessions at once)