Quoting Wenbing Zhao <[EMAIL PROTECTED]>:
Thanks a lot Zhao! I didn't have time to look into this.
The reason the coordinator was kept even after completion of the transaction
was, the at-specification requires that we respond to late messages from
participants. I guess we need to look for a better way to do this. Keeping the
coordinator is just an easy but inefficient way of doing it.
thanks again.
--dasarath
> 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?
>
> DIV { MARGIN:0px;} Hi Zhao,
>
> has this bug been fixed ?
>
> thanks
>
> Valerio
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
