Andreas Hartmann wrote:
Richard Frovarp schrieb:
Andreas Hartmann wrote:
Hi Lenya devs,
IMO the only reasonable solution to this problem is to isolate the
sessions for each accreditable manager and allow multiple parallel
authenticated identities. The cleanest solution might be to use a
dedicated servlet for each publication, but this would probably make
the application deployment and management much more complicated. A
simpler approach would be to use the accreditable manager ID as part
of the session attribute name, e.g.:
String accrMgrId = accreditableManager.getId();
String key = Identity.class.getName() + "/" + accrMgrId;
session.setAttribute(key, identity);
When a request is processed, only the identity for the corresponding
accreditable manager is taken into account. This looks a bit
strange, though – we're kind-of replicating the servlet engine's
session management on the application level.
Separate servlets would be a killer and should be avoided. Pairing
the accreditable manager with the ID works for me.
Do we still have a problem with the sessions growing out of control?
I hope we could mitigate it by changing most of the tab usecases not
to use continuations. Does anybody still run into memory issues?
-- Andreas
The version that my old job uses is quite old. I did go through and
modify several of the usecases to not use continuations and I think it
helped some. They probably won't have good data until next August
though. It was really bad when we had about 100 people logged in for 4
hours straight. I probably should do some testing.
Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lenya.apache.org
For additional commands, e-mail: dev-h...@lenya.apache.org
