Swapping a session on a direct action
Swapping a session on a direct action
- Subject: Swapping a session on a direct action
- From: Miguel Arroz <email@hidden>
- Date: Mon, 7 Apr 2008 11:18:29 +0100
Hi!
We're having a problem with "zombie" sessions. One of our direct
actions has some trickery to always create a new session, even if the
wosid cookie has a valid session ID, and I believe something is acting
up there, but I can't figure out why (yes, this looks strange, but we
actually know what we are doing, or at least we like to believe so).
The problem is this: everytime I access that DA, JavaMonitor shows
2 more sessions on that instance. After the typical 60 minutes, one of
the sessions dies, but the other remains forever. This has obvious
serious consequences, as Refuse New Sessions will wait for every
session to die, and those zombie sessions simply won't go away.
As I needed a more sophisticated way to track sessions (I need to
know the user login, etc) I built my own session tracker, that hooks
into session's sleep and termination methods to keep track of what's
going on. Looking at the table generated by that tracker, everything
is fine: no zombie sessions appear, and all the sessions die after 60
minutes.
So, to dig this further, what I want to know is where does that
active session counter on JavaMonitor comes from. How's that count
being made? Is it done on the app or on wotaskd?
Yours
Miguel Arroz
Miguel Arroz
http://www.terminalapp.net
http://www.ipragma.com
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden