Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <26070604.15561273555650207.JavaMail.jira@thor>
Date: Tue, 11 May 2010 01:27:30 -0400 (EDT)
From: "Jed Wesley-Smith (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Updated: (FELIX-2332) Lots of contention on
 ExtensionManager.openConnection(URL)
In-Reply-To: <31137117.15231273555349293.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jed Wesley-Smith updated FELIX-2332:
------------------------------------

    Attachment: ExtensionManager.java.patch

attached is a simple patch that reduces the scope of the sync block to the iteration.

> Lots of contention on ExtensionManager.openConnection(URL)
> ----------------------------------------------------------
>
>                 Key: FELIX-2332
>                 URL: https://issues.apache.org/jira/browse/FELIX-2332
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>            Reporter: Jed Wesley-Smith
>         Attachments: ExtensionManager.java.patch
>
>
> This method is synchronized, apparently to protect is the iteration through the m_extensions list. We have seen significant blocking in our applications as this lock encompasses the call to URL.openConnection as well.
> As this list is rarely changed, a copy-on-write structure would be more appropriate, but at the very least the, only holding the lock during the iteration would be far preferable.

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