You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2015/10/12 22:14:05 UTC
[jira] [Resolved] (QPIDJMS-123) Potential thread safety issue in
the QueueBrowser implementation
[ https://issues.apache.org/jira/browse/QPIDJMS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved QPIDJMS-123.
----------------------------------
Resolution: Fixed
Assignee: Timothy Bish
Fix Version/s: 0.7.0
Moved some things around and made the access to the internal consumer safer.
> Potential thread safety issue in the QueueBrowser implementation
> -----------------------------------------------------------------
>
> Key: QPIDJMS-123
> URL: https://issues.apache.org/jira/browse/QPIDJMS-123
> Project: Qpid JMS
> Issue Type: Bug
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 0.7.0
>
>
> The QueueBrowser implementation creates an internal JmsMessageConsumer instance and the management of that instance and its usage appears to suffer from some potential thread safety issues is the QueueBrowser is used by multiple threads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org