activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3703) Replace use of class Valve with standard JDK ReentrantReadWriteLock in class Topic.java
Date Mon, 06 Feb 2012 22:56:59 GMT

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

Timothy Bish resolved AMQ-3703.
-------------------------------

    Resolution: Fixed

Fix applied in trunk.
                
> Replace use of class Valve with standard JDK ReentrantReadWriteLock in class Topic.java
> ---------------------------------------------------------------------------------------
>
>                 Key: AMQ-3703
>                 URL: https://issues.apache.org/jira/browse/AMQ-3703
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.5.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Trivial
>             Fix For: 5.6.0
>
>
> The Topic class uses an old AMQ class Valve that is essentially a pre JDK 1.5 Read /
Write lock.  The JDK RW lock is much more efficient than ours using only a single CAS operation
in many cases when multiple readers need access to the lock as opposed to the Valve class
that requires all threads to synchronize and possibly wait on a monitor.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message