• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

tomcat monitor

 
gana rajan
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
can someone please suggest me an open source which able to detect the active http session or active user in tomcat? and give notification when the server is going to disconnect.
i've tried javamelody,lambdaprobe,messadmin, session monitor, jamon, and dynamicselectlist.

messadmin was good open source. but, when i install and tried to use. it's not working as they didnt provide full installation guide.
javamelody did not show any active http session at all.
lamdaprobe: it did not record the active session.

please someone help me. i've been in this for weeks. i need to finish by tomorrow. please.

thanks in advance.
 
Ulf Dittmer
Rancher
Posts: 42968
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
PSI-Probe has the number of sessions; it's a newer version of LambdaProbe.
 
gana rajan
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i'm using version 2.3.1.
where i can find the number of session?
 
gana rajan
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
thanks in advance
 
Tim Holloway
Saloon Keeper
Pie
Posts: 18226
53
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"Disconnect" is technically incorrect. HTTP disconnects after each and every HTTP[S] request/response cycle (page or AJAX request). The HttpSession object gives the illusion of a continuous connection by maintaining an identity and a context that can be passed back and forth between client and server on successive request cycles. However, the web is not true client/server, and there's no application code executing when a request is not actively being processed, except where independent disconnected threads were spawned. Which is outside of this topic.

A user session ends when either the application explicitly requests it (session.invalidate()) or when no request has been made for that session within the webapp-configured timeout period. Since there's no client connection to break, the actual destruction of the session would then occur whenever the server found it convenient, rather than being guaranteed to happen exactly at the expiration of the session period.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic