[
https://issues.apache.org/jira/browse/WICKET-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210910#comment-15210910
]
ASF GitHub Bot commented on WICKET-6128:
----------------------------------------
Github user klopfdreh commented on the pull request:
https://github.com/apache/wicket/pull/166#issuecomment-201007248
Integrated:
master:
https://github.com/apache/wicket/commit/50b6cadc5d44a45c261f599501cac20b5c20c766
wicket-7.x:
https://github.com/apache/wicket/commit/20c3b9982dffbb265bb176439414622169b1533a
@martin-g - One thing which has to be done so that the measurement of the
session is working correctly is to clear the session storage from disc after
restarting the server, because otherwise stored session leads to negative
session counts, because they are restored and expire.
There is no good solution to handle this out of the box by the servlet API,
because anywhere you persist the information about a session count it can be
erased. (tmp folder, realPath(), etc.)
I made a hint into the guide. I also removed the jsessionid from the path
of the request measurement.
> Add metrics for currently active sessions
> -----------------------------------------
>
> Key: WICKET-6128
> URL: https://issues.apache.org/jira/browse/WICKET-6128
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-metrics
> Affects Versions: 7.2.0, 8.0.0-M1
> Reporter: Martin Grigorov
> Assignee: Tobias Soloschenko
> Priority: Minor
> Fix For: 7.3.0, 8.0.0-M1
>
>
> Add metric for the number of currently active Wicket sessions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
