axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] Moved: (TRANSPORTS-2) JMSSender should not use a shared session or producer
Date Wed, 25 Aug 2010 10:47:15 GMT


Andreas Veithen moved WSCOMMONS-473 to TRANSPORTS-2:

          Project: Axis2 Transports  (was: WS-Commons)
              Key: TRANSPORTS-2  (was: WSCOMMONS-473)
    Fix Version/s: 1.1.0
                       (was: Transports 1.1)
      Component/s: JMS
                       (was: Transport)

> JMSSender should not use a shared session or producer
> -----------------------------------------------------
>                 Key: TRANSPORTS-2
>                 URL:
>             Project: Axis2 Transports
>          Issue Type: Bug
>          Components: JMS
>            Reporter: Andreas Veithen
>            Priority: Critical
>             Fix For: 1.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]

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message