You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2017/05/03 22:39:04 UTC

[jira] [Commented] (AXIS2-5524) JMSSender should not use a shared session or producer

    [ https://issues.apache.org/jira/browse/AXIS2-5524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995819#comment-15995819 ] 

Andreas Veithen commented on AXIS2-5524:
----------------------------------------

The patch is incomplete because
* the documentation still mentions the cache levels "session" and "producer" (as well as "consumer");
* the code that parses the removed cache levels is still present.

> JMSSender should not use a shared session or producer
> -----------------------------------------------------
>
>                 Key: AXIS2-5524
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5524
>             Project: Axis2
>          Issue Type: Bug
>          Components: JMS transport
>            Reporter: Andreas Veithen
>            Priority: Critical
>         Attachments: AXIS2-5524.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.3.15#6346)

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