[
https://issues.apache.org/jira/browse/QPID-7905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall closed QPID-7905.
----------------------------
Resolution: Won't Fix
Marking Won't Fix. Use newer Qpid JMS Client (AMQ1.0)
https://qpid.apache.org/components/jms/index.html
> [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
>
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
