JMSSender should not use a shared session or producer
-----------------------------------------------------
Key: WSCOMMONS-473
URL: https://issues.apache.org/jira/browse/WSCOMMONS-473
Project: WS-Commons
Issue Type: Bug
Components: Transport
Reporter: Andreas Veithen
Priority: Critical
Fix For: Transports 1.0
Depending on the cache level, the JMSConnectionFactory stores a "shared"
session and/or message producer. These objects are used by the JMSSender (via
JMSMessageSender). Since sessions and producers are not thread safe, this will
lead to concurrency issues. Note that initially the JMSListener used a similar
pattern. This has been corrected [1], but the issue has never been addressed
for the JMSSender. The concept of "shared" session/producer should be
eliminated altogether from JMSConnectionFactory.
[1] http://markmail.org/message/umhenrurlrekk5jh
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
