[jbossts-issues] [JBoss JIRA] Commented: (JBTM-294) Remove redundant finalize methods invoked duinrg JTA operation and document removal in release notes

Andrew Dinn (JIRA) jira-events at lists.jboss.org
Sat Oct 6 11:12:03 EDT 2007

    [ http://jira.jboss.com/jira/browse/JBTM-294?page=comments#action_12380850 ] 
Andrew Dinn commented on JBTM-294:

These methods have been removed to avoid GC performance problems under high transaction throughput.. If a large number of transactions are executed between garbage collects then the requirement to finalize these instances can cause large numbers of them to become retained across nursery space collections and, eventually, to be tenured, resulting in more frequent full collections. Furthermore, writes to tenured instances during finalize operations can potentially interfere with the concurrent scan of tenured space, requiring a lot of rescanning.
As a result of these changes
  i) several debug messages about unreferenced instances will no longer be output (classes Mutex, ActionHierarchy, ReaperElement)
  ii) class RecordList no longer calls method empty() to pop() elements from unreferenced instances
  iii) class Mutex no longer notifies threads waiting on unreferenced instances
Although these constitute a (minor) change to existing behaviour  they should not affect correctly programmed applications. All such programs stand to benefit form the resulting performance enhancements.

> Remove redundant finalize methods invoked duinrg JTA operation and document removal in release notes
> ----------------------------------------------------------------------------------------------------
>                 Key: JBTM-294
>                 URL: http://jira.jboss.com/jira/browse/JBTM-294
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.2.3
>            Reporter: Andrew Dinn
>         Assigned To: Andrew Dinn
>             Fix For: 4.4
> Remove redundant finalize methods from the following classes:
>     com.arjuna.ats.arjuna.common.Mutex.java
>     com.arjuna.ats.arjuna.coordinator.RecordList.java
>     com.arjuna.ats.arjuna.coordinator.ActionHierarchy.java
>     com.arjuna.ats.internal.arjuna.coordinator.ReaperElement.java
>     com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.java
> and document their removal in the relevant release notes.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbossts-issues mailing list