qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-7905) [Java Client AMQP 0-x] Connection#start is not thread-safe
Date Tue, 07 Nov 2017 16:55:00 GMT

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

Keith Wall updated QPID-7905:
    Fix Version/s: qpid-java-client-0-x-6.3.0

> [Java Client AMQP 0-x] Connection#start is not thread-safe
> ----------------------------------------------------------
>                 Key: QPID-7905
>                 URL: https://issues.apache.org/jira/browse/QPID-7905
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>            Reporter: Lorenz Quack
>            Priority: Critical
>             Fix For: qpid-java-client-0-x-6.3.0
> The JMS spec says that Connections may be used from several threads concurrently.
> However, our implementation of {{Connection#start}} is currently not thread-safe. It
iterates over its list of sessions and calls {{Session#start}}. The session rightfully (this
is specified in the JMS spec as well) assumes that it is being called from a single thread.
> An example of the impact of this is that a session can be used (by {{Connection#start}})
after it has been closed (via {{Session#close}}) leading to an Exception due to the broker
receiving a frame with an unknown {{channelId}}.
> Note: The comment on {{Connection#start}} stating that JMS allows for non thread-safe
implementations seems to be in error!

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message