You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <ji...@apache.org> on 2013/05/18 00:11:15 UTC
[jira] [Resolved] (QPID-4864) The JMS client shouldn't hold a lock
when creating a messge
[ https://issues.apache.org/jira/browse/QPID-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu resolved QPID-4864.
------------------------------------
Resolution: Fixed
Removed the lock. Fix committed at http://svn.apache.org/r1483877
> The JMS client shouldn't hold a lock when creating a messge
> -----------------------------------------------------------
>
> Key: QPID-4864
> URL: https://issues.apache.org/jira/browse/QPID-4864
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.16, 0.18, 0.20, 0.22
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.23
>
>
> The JMS client needlessly holds the failover mutex when creating a text message. It also sets the session.
> When creating messages to be sent, they should be just value objects and should not hold any state.
> When constructing a message to be given to the consumer, we have to set the session, so acknowledge can be called. But not when we create messages for sending.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org