Monitoring client HTTP session statistics
You can monitor user session activity for web applications that are running on your server.
Before you begin
About this task
- Stand-alone installation in which WebSphere eXtreme Scale is using another application server
- Integrated installation in which WebSphere eXtreme Scale is using WebSphere Application Server as the application server
Depending on how you have deployed WebSphere eXtreme Scale, you can
monitor different types of session activities:
- When using WebSphere eXtreme Scale with another application server, you
can monitor the following counters:
Table 1. HTTP Session Statistic Types Name Description createCount The number of sessions that were created. invalidateCount The number of sessions that were invalidated. activeCount The number of concurrently active sessions. A session is active if the WebSphere Application Server is currently processing a request that uses that session. liveCount The number of local sessions that are currently cached in memory from the time at which this metric is enabled cacheDiscardCount The number of session objects that have been forced out of the cache. A least recently used (LRU) algorithm removes old entries to make room for new sessions and cache misses. Applicable only for persistent sessions. affinityBreakCount The number of requests that are received for sessions that were last accessed from another Web application. This value can indicate failover processing or a corrupt plug-in configuration. timeoutInvalidationCount The number of sessions that are invalidated by timeout. activateNonExistSessionCount The number of requests for a session that no longer exists, presumably because the session timed out. Use this counter to help determine if the timeout is too short. - When you are using WebSphere Application Server, you can monitor the following counters: Servlet session counters.
Procedure
Depending on how you have deployed WebSphere eXtreme Scale you can enable HTTP client session statistics in one of the following ways:
What to do next
com.ibm.websphere.objectgrid:type=Session,name=webAppContextRoot
You can view the
MBean using the one of the following tools:
- Access MBean statistics using the wsadmin tool.
For more information, see Accessing Managed Beans (MBeans) using the wsadmin tool.
- Access MBean statistics programmatically.
For more information, see Accessing Managed Beans (MBeans) programmatically.
- Access MBean statistics with tools such as JConsole (Java Monitoring and Management Console).