() for condition check
Correct me if wrong... Thanks for sharing!!
Cheers
Cheong Hee
- Original Message -
From: "Chuck Hill"
To: "Cheong Hee (Gmail)"
Cc:
Sent: Wednesday, July 22, 2009 2:00 PM
Subject: Re: Inaccurate active session count in JavaMonitor (Solved)
Hill" >
To: "Cheong Hee (Gmail)"
Cc:
Sent: Tuesday, July 21, 2009 10:04 PM
Subject: Re: Inaccurate active session count in JavaMonitor (Solved)
On Jul 21, 2009, at 2:44 AM, Cheong Hee (Gmail) wrote:
Yeap, exception found.
lockManager.unlock() throws IllegalStateExcepti
makeStrongReferences
findReference
emptyUnregisterQueue
sameThreadAssert
Cheers
Cheong Hee
- Original Message -
From: "Chuck Hill"
To: "Cheong Hee (Gmail)"
Cc:
Sent: Tuesday, July 21, 2009 10:04 PM
Subject: Re: Inaccurate active session count in JavaMonitor (Solved)
On Jul
On Jul 21, 2009, at 2:44 AM, Cheong Hee (Gmail) wrote:
Yeap, exception found.
lockManager.unlock() throws IllegalStateException when lock count is
zero.
Which says to me that it was not locked to begin with. Try
if (lockManager.isLocked()) {
lockManager.unlock();
}
When the lock co
Yeap, exception found.
lockManager.unlock() throws IllegalStateException when lock count is zero.
When the lock count is > 1, MultiEC lock manager is happier to unlock all
ECs, but not when lock count=0. Try to relate why the lock count=0 is
handled by exception. Is it acting like an insuran
And just checked my
code that no WOSession has been declared in any wocomponent.
You want to look at the code BEFORE the call to super.
Chuck
- Original Message - From: "Chuck Hill" >
To: "Cheong Hee (Gmail)"
Cc:
Sent: Saturday, July 18, 2009 1:27 AM
Subje
t;Cheong Hee (Gmail)"
Cc:
Sent: Saturday, July 18, 2009 1:27 AM
Subject: Re: Inaccurate active session count in JavaMonitor
On Jul 17, 2009, at 10:15 AM, Cheong Hee (Gmail) wrote:
Adding the code as mentioned earlier, I have run three sessions with the
following conditions:
session1:
rk Ritchie" >
To: "Chuck Hill"
Cc: "Cheong Hee (Gmail)" ; >
Sent: Thursday, July 16, 2009 4:56 PM
Subject: Re: Inaccurate active session count in JavaMonitor
On 15-Jul-09, at 9:21 AM, Chuck Hill wrote:
The memory usage stats are meaningless, but the active session
On Jul 17, 2009, at 10:15 AM, Cheong Hee (Gmail) wrote:
Adding the code as mentioned earlier, I have run three sessions with
the following conditions:
session1: log out gracefully by the user
session2: time out occurs
session3: time out occurs
The sequence of sessions are session1, following
Adding the code as mentioned earlier, I have run three sessions with the
following conditions:
session1: log out gracefully by the user
session2: time out occurs
session3: time out occurs
The sequence of sessions are session1, following by session2 and then
session3.
When session1 is terminat
has set to -WOSessionTimeOut as 90. In fact, when I
did a proper log out, the count is reduced in JavaMonitor. Thanks all
and will try it out with code given.
- Original Message - From: "Mark Ritchie"
To: "Chuck Hill"
Cc: "Cheong Hee (Gmail)" ;
>
Sent
Monitor. Thanks all and will try it out with code given.
- Original Message - From: "Mark Ritchie" >
To: "Chuck Hill"
Cc: "Cheong Hee (Gmail)" ; >
Sent: Thursday, July 16, 2009 4:56 PM
Subject: Re: Inaccurate active session count in JavaMonit
Hee (Gmail)" ; >
Sent: Thursday, July 16, 2009 4:56 PM
Subject: Re: Inaccurate active session count in JavaMonitor
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 y
(Gmail)" ;
Sent: Thursday, July 16, 2009 4:56 PM
Subject: Re: Inaccurate active session count in JavaMonitor
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
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.
; >
To: "Cheong Hee (Gmail)"
Cc:
Sent: Thursday, July 16, 2009 12:21 AM
Subject: Re: Inaccurate active session count in JavaMonitor
On Jul 15, 2009, at 2:14 AM, Cheong Hee (Gmail) wrote:
I believe most have observed the active session count in
JavaMonitor is not accurate when
-
From: "Chuck Hill"
To: "Cheong Hee (Gmail)"
Cc:
Sent: Thursday, July 16, 2009 12:21 AM
Subject: Re: Inaccurate active session count in JavaMonitor
On Jul 15, 2009, at 2:14 AM, Cheong Hee (Gmail) wrote:
I believe most have observed the active session count in JavaMonit
On Jul 15, 2009, at 2:14 AM, Cheong Hee (Gmail) wrote:
I believe most have observed the active session count in JavaMonitor
is not accurate when the session is ended due to time out. The
count reduced if the session terminate e.g. user log out. I have
not tried it out but it is quite obv
I believe most have observed the active session count in JavaMonitor is not
accurate when the session is ended due to time out. The count reduced if
the session terminate e.g. user log out. I have not tried it out but it is
quite obvious this count may be taken from Application.activeSessionCo
19 matches
Mail list logo
