[
https://issues.apache.org/jira/browse/QPIDJMS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965064#comment-15965064
]
ASF subversion and git services commented on QPIDJMS-283:
---------------------------------------------------------
Commit 091aa1df304a2c954593e6a4e418bc40dbd392e9 in qpid-jms's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=091aa1d ]
QPIDJMS-283 Ensure new TX started whenever there is pipelined failure
When offline the failover provider allows rollback to complete normally
as the TX has been terminated already so the command doesn't need to be
held. We need to ensure that when these states happen we still look and
begin a new TX which will wait for connection restoration to complete.
> Pipeline the declare that follows a transaction discharge for quicker
> processing
> --------------------------------------------------------------------------------
>
> Key: QPIDJMS-283
> URL: https://issues.apache.org/jira/browse/QPIDJMS-283
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.21.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 0.22.0
>
>
> For the normal commit / rollback case we can send an immediate Declare of a
> new transaction to speed up the message rate when operating inside a
> transacted session.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
