-
1. Re: limit number of http sessions
mlybarger Apr 1, 2015 11:22 PM (in response to mlybarger)i've been doing more research. it seems that all <passivation-config> was deprecated (no longer used).
so, i looked to the source code of undertow, and i find the InMemorySessionManager has an option for: exictOldestUnusedSessionOnMax.
if this gets set to false, it rejects the connections per my understanding of lines 132-135 in the code:
the question remains; how to set this to false...?
-
2. Re: limit number of http sessions
pferraro Apr 6, 2015 8:21 AM (in response to mlybarger)This behavior was changed in this commit[1]. Apart from the misspelling (seems like a cross between evict and expire), I think the default behavior (WildFly does not currently contain a mechanism to override it[2]) should really be false, since this new behavior is counter to the servlet specification which states that sessions should remain active until the configured session-timeout.
Regarding passivation, this was deprecated in WF8, since the value is easily implied by max-active-sessions. If this is non-zero, and your web application is distributable (requiring your session attributes to be serializable), then any sessions in excess of max-active-sessions will passivate.
[1] Make behaviour on hitting max sessions customisable · undertow-io/undertow@4c7915d · GitHub
[2] wildfly/UndertowDeploymentProcessor.java at master · wildfly/wildfly · GitHub
-
3. Re: limit number of http sessions
mlybarger Apr 6, 2015 3:32 PM (in response to pferraro)This is VERY helpful, thanks. However, I don't see where exictOldestUnusedSessionOnMax ever gets set to false. The factory that creates the InMemorySessionManager doesn't seem to allow use of the new constructor.
-
4. Re: limit number of http sessions
pferraro Apr 6, 2015 4:28 PM (in response to mlybarger)This is what I meant by: "WildFly does not currently contain a mechanism to override it[2]". I've opened: