Re: memory leakage?

Mon, 09 Oct 2006 01:01:15 -0700

thank you soo much
 
Valerio
----- Original Message -----
Sent: Monday, October 09, 2006 6:41 AM
Subject: Re: memory leakage?

Valerio,

Sorry to respond to you so late. I just found your email in the spam folder. Yes,
the bug is fixed. In addition to the fix Dasarath put in, you need to explicitly remove
the callback objects from the CallbackRegistry whenever the transaction is completed.
It is a bad idea to depend on the CallbackRegisstry's timeout to remove these
entries because by the timeout the memory might already be too bloated if the load
is high. Below is a few specific fixes:

In src/java/org/apache/kandula/coordinator/at/TransactionImpl.java, within
the CompletionInitiatorCallback inner class, in committedOperation(),
abortedOperation(), timeout() and onFault() methods, add:

CallbackRegistry.getInstance().remove(this);

This is to avoid memory leak for the completion initiator. Do similar modification
for the transaction participants:
/src/java/org/apache/kandula/coordinator/at/AbstractParticipant.java,
in commitOperation(), rollbackOperation(), timeout(), and onFault() methods, add:

CallbackRegistry.getInstance().remove(this);

before EVERY return statement.

--- Wenbing Zhao



----- Original Message ----
From: Valerio Vianello <[EMAIL PROTECTED]>
To: Wenbing Zhao <[EMAIL PROTECTED]>
Sent: Monday, September 11, 2006 10:28:25 AM
Subject: Re: memory leakage?

Hi Zhao,
 
has this bug been fixed ?
 
thanks
 
Valerio


Reply via email to