Frankly I don't want to delve too deep into this. Eg, one problem may
occur when you have wosid's both in the cookies and in the url and
they don't match. Or if a restore fails and a new session is created
and the cookie is still wrong - and you have an exception later where
the error handler terminates the session...
All I wanted to say was that WOContext.hasSession() is not to be
relied on in some cases.
Cheers, Anjo
Am 07.02.2008 um 22:55 schrieb Thomas:
> thanks, but with new knowledge comes confusion...
>
> I only cared about direct actions, because I thought component
> actions were magically taken care of. I assumed that as soon as
> "Refuse new sessions" was set in JavaMonitor for instance X,
> component requests that did not have a session were passed on to
> another instance without ever getting to instance X. Back in the
> days before I had session cookies and a lot of direct actions, that
> was the way it worked for me. But now I am seeing some new sessions
> being created by component actions in instance X, possibly because
> of session cookies from a different instance.
>
> Am I wrong in my assumptions about component requests? Am I going to
> have to check every single request, both direct action and
> component? That doesn't sound right.
>
> In fact, surely the best result would be "magically" make direct
> actions work the way I thought component actions worked, so that
> clicking "Refuse new sessions" just worked...
This archive was generated by hypermail 2.0.0 : Thu Feb 07 2008 - 17:09:18 EST