|Anonymous | Login | Signup for a new account||08-21-2019 21:53 PDT|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Simple Details [ Jump to Notes ]||[ View Advanced ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0002137||[Resin]||minor||always||11-02-07 08:30||06-11-08 23:16|
|Summary||0002137: session unbound|
(rep by Kair Virkki)
And to add to this, I noticed that in my cluster setup, both
valueUnbound and sessionDestroyed get called when i shutdown the Resin
node that the session is currently on. I don't think this is
appropriate since the user's session will continue fine on the other
Resin node. I have a problem here, because I need to release some
resources when user session REALLY ends, not when one of the nodes
Is there any work-around for this weird Resin behavior?? How can I
listen to the session FINALLY ending in a cluster??
2007/10/31, Kai Virkki <email@example.com>:
I noticed that the issue with unBound being called is fixed from 3.1.2 -> 3.1.3.
0001820: valueBound isn't called on load from persistent store anymore
but valueUnbound still is called on save
We have the same problem on 3.0.23. Could it be fixed to the
production branch too?
|11-02-07 08:30||ferg||New Issue|
|06-11-08 23:16||ferg||Note Added: 0003181|
|06-11-08 23:16||ferg||Assigned To||=> ferg|
|06-11-08 23:16||ferg||Status||new => closed|
|06-11-08 23:16||ferg||Resolution||open => fixed|
|06-11-08 23:16||ferg||Fixed in Version||=> 3.2.0|
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed.|
25 unique queries executed.