You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commons-dev@ws.apache.org by "Ruwan Linton (JIRA)" <ji...@apache.org> on 2009/09/22 11:30:09 UTC

[jira] Updated: (WSCOMMONS-473) JMSSender should not use a shared session or producer

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

Ruwan Linton updated WSCOMMONS-473:
-----------------------------------

    Fix Version/s:     (was: Transports 1.0)
                   Transports 1.1

This will be fixed for the Transports version 1.1

> 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.1
>
>
> 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.