Web Application Monitoring in WildFly: Difference between revisions
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
Web applications deployed as part of a WAR deployment in JBoss are automatically instrumented to expose relevant runtime [[#JMX|JMX]] statistics on the JMX bus and in [[#CLI|CLI]]. These statistics refer mostly to HTTP session (created sessions, max active sessions, expired sessions, session maximum and average alive time), but other information such as the virtual host or the context root is exposed. | Web applications deployed as part of a WAR deployment in JBoss are automatically instrumented to expose relevant runtime [[#JMX|JMX]] statistics on the JMX bus and in [[#CLI|CLI]]. These statistics refer mostly to HTTP session (created sessions, max active sessions, expired sessions, session maximum and average alive time), but other information such as the virtual host or the context root is exposed. | ||
<span id="Clustered_Web_Applications"></span>If the web application is '''clustered''' (declared <distributable>), the CLI/JMX session metric are ''cluster-wide'' metrics. For example, active session refers to the number of active sessions across the entire cluster. | |||
Revision as of 16:27, 11 May 2017
External
- How to monitor HTTP Sessions to count / view the number of active HTTP sessions in JBoss EAP https://access.redhat.com/solutions/22091
Internal
Relevance
- EAP 6.4.10
Overview
Web applications deployed as part of a WAR deployment in JBoss are automatically instrumented to expose relevant runtime JMX statistics on the JMX bus and in CLI. These statistics refer mostly to HTTP session (created sessions, max active sessions, expired sessions, session maximum and average alive time), but other information such as the virtual host or the context root is exposed.
If the web application is clustered (declared <distributable>), the CLI/JMX session metric are cluster-wide metrics. For example, active session refers to the number of active sessions across the entire cluster.