felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (FELIX-908) Unsynchronize access to bundle state inside BundleInfo by making the variable volatile
Date Tue, 03 Feb 2009 16:43:59 GMT

     [ https://issues.apache.org/jira/browse/FELIX-908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Richard S. Hall resolved FELIX-908.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: felix-1.6.0
         Assignee: Richard S. Hall

I committed a patch to trunk to make access to bundle state volatile. Please close this issue
if you are satisfied.

> Unsynchronize access to bundle state inside BundleInfo by making the variable volatile
> --------------------------------------------------------------------------------------
>
>                 Key: FELIX-908
>                 URL: https://issues.apache.org/jira/browse/FELIX-908
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: felix-1.2.1

>            Reporter: Anatoli Kazatchkov
>            Assignee: Richard S. Hall
>            Priority: Minor
>             Fix For: felix-1.6.0
>
>         Attachments: bundle_info.patch
>
>
> Synchronized access to bundle state inside {{BundleInfo}} class creates an unnecessary
contention point in environments where {{bundle.getState()}} is called a lot.
> Declaring {{m_state}} variable volatile and removing synchronization from {{setState()}}
and {{getState()}} will do the trick.I will attach the patch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message