You are viewing a plain text version of this content. The canonical link for it is here.

Posted to xbean-dev@geronimo.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2007/03/12 15:03:09 UTC

[jira] Closed: (XBEAN-83) NamedClassLoader.isDestroyed should not be synchronized

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

Guillaume Nodet closed XBEAN-83.
--------------------------------

    Resolution: Fixed

$ svn commit -m "XBEAN-83: NamedClassLoader.isDestroyed should not be synchronized"
Sending        xbean-classloader/src/main/java/org/apache/xbean/classloader/NamedClassLoader.java
Transmitting file data .
Committed revision 517223.

> NamedClassLoader.isDestroyed should not be synchronized
> -------------------------------------------------------
>
>                 Key: XBEAN-83
>                 URL: https://issues.apache.org/jira/browse/XBEAN-83
>             Project: XBean
>          Issue Type: Improvement
>          Components: classloader
>    Affects Versions: 2.8
>            Reporter: Guillaume Nodet
>         Assigned To: Guillaume Nodet
>             Fix For: 3.0
>
>
> There is not much value added to synchronize this method, while
> under heavy load, it really becomes a bottleneck when calling
>    getResource, loadClass, findResources, etc ...

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