[
https://issues.apache.org/jira/browse/QPIDJMS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943586#comment-14943586
]
ASF subversion and git services commented on QPIDJMS-120:
---------------------------------------------------------
Commit febb811d93cb2a502b115d9349cfc90ccb610370 in qpid-jms's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=febb811 ]
QPIDJMS-120: while in here, make lock field private and final
> viewer may not see previously updated running/closed state on local queue
> -------------------------------------------------------------------------
>
> Key: QPIDJMS-120
> URL: https://issues.apache.org/jira/browse/QPIDJMS-120
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.5.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Minor
> Fix For: 0.6.0
>
>
> The client keeps a local queue for messages as they arrive. Most of the
> methods in the class synchronize around various state governing the behaviour
> ot the queue, such as whether it is 'running' or 'closed'. It is possible to
> view this state via isClosed() and isRunning() methods, hopwever these do not
> synchronise in the same way, meaning one thread (e.g the app thread) viewing
> these states may not see a previous update by another thread (e.g the client).
> These methods are only used in a couple of places, and reading a stale value
> will typically only lead to further use of the queue (using methods which are
> synchronized around the state), so this shouldnt really cause significant
> issue, but it would be better to ensure the updates are seen promptly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
