Good pointer, I had overlooked this as the multiEC is implemented at the
later code. Thanks!
- Original Message -
From: "Jean-Francois Veillette"
To: "Cheong Hee (Gmail)"
Cc: "Mark Ritchie" ; "Chuck Hill"
;
Sent: Thursday, July 16, 2009 8:51 PM
Subject: Re: Inaccurate active sess
Better still, use a try...finally to be certain that the call to
super.terminate happens:
On Jul 16, 2009, at 5:51 AM, Jean-Francois Veillette wrote:
There is a potential problem if logOnUser is an eo registered in an
editingContexte that is unlock() earlier in the method.
What you could d
There is a potential problem if logOnUser is an eo registered in an
editingContexte that is unlock() earlier in the method.
What you could do is :
public void terminate() {
String audit = null;
if (logOnUser != null)
audit = "User " + logOnUser.vName() + " is lo
I just confirmed and checked my code that session.terminate() has overriden
as the following:
/**
* unlock ec when terminates.
*/
public void terminate() {
lockManager().unlock();
_multiECLockManager = null;
//RSP07042006
if (logOnUser != null)
On 15-Jul-09, at 9:21 AM, Chuck Hill wrote:
The memory usage stats are meaningless, but the active session count
has been accurate in my experience. I suspect that your code has
bugs in it that are preventing session termination. Get a thread
dump and see if you have deadlocked threads.
