You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2013/03/29 10:59:16 UTC
[jira] [Resolved] (QPID-4609) Incorrect lock in the synchronize
statement in org.apache.qpid.server.model.adapter.BrokerAdapter
[ https://issues.apache.org/jira/browse/QPID-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPID-4609.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.21
Seems good to me.
> Incorrect lock in the synchronize statement in org.apache.qpid.server.model.adapter.BrokerAdapter
> -------------------------------------------------------------------------------------------------
>
> Key: QPID-4609
> URL: https://issues.apache.org/jira/browse/QPID-4609
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.21
> Reporter: JAkub Scholz
> Assignee: Robbie Gemmell
> Priority: Minor
> Fix For: 0.21
>
>
> The getTrustStores() and getKeyStores() methods of the BrokerAdapter class seem use both the _trustStores object as a lock for the sychronize statement:
> @Override
> public Collection<KeyStore> getKeyStores()
> {
> synchronized(_trustStores)
> {
> return Collections.unmodifiableCollection(_keyStores.values());
> }
> }
> @Override
> public Collection<TrustStore> getTrustStores()
> {
> synchronized(_trustStores)
> {
> return Collections.unmodifiableCollection(_trustStores.values());
> }
> }
> Is that a bug? I would assume that the getKeyStores method should use the _keyStores object instead of _trustStores.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org