| Summary: | _maxIdleMs overlaps when bi session times | ||
|---|---|---|---|
| Product: | [RT] Jetty | Reporter: | Mathieu Carbou <mathieu.carbou> |
| Component: | server | Assignee: | Greg Wilkins <gregw> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | P3 | CC: | jetty-inbox, mathieu.carbou |
| Version: | unspecified | ||
| Target Milestone: | 7.5.x | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Mathieu Carbou
If you want big session time, you can use subclass AbstractSession and call just after the constructor super.setMaxInactiveInterval to reset the bad values that has been put in maxIdleMs to the good one.
public abstract class SessionSkeleton extends AbstractSession {
public SessionSkeleton(HttpServletRequest request) {
super(SessionManagerSkeleton.this, request);
super.setMaxInactiveInterval(SessionManagerSkeleton.this._dftMaxIdleSecs > 0 ? SessionManagerSkeleton.this._dftMaxIdleSecs : -1);
}
thanks. Will be in 7.6 and 8.1 |