Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E657310EAB for ; Tue, 15 Oct 2013 06:38:59 +0000 (UTC) Received: (qmail 23655 invoked by uid 500); 15 Oct 2013 06:38:58 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 23371 invoked by uid 500); 15 Oct 2013 06:38:49 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 23276 invoked by uid 99); 15 Oct 2013 06:38:44 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Oct 2013 06:38:44 +0000 Date: Tue, 15 Oct 2013 06:38:44 +0000 (UTC) From: "Remo Gloor (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMQNET-450) NetTxTransaction replay is incorrect when using Failover Transport MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Remo Gloor created AMQNET-450: --------------------------------- Summary: NetTxTransaction replay is incorrect when using Failover Transport Key: AMQNET-450 URL: https://issues.apache.org/jira/browse/AMQNET-450 Project: ActiveMQ .Net Issue Type: Bug Reporter: Remo Gloor Assignee: Jim Gomes TransactionState.AddCommand must clone the operation because TransactionInfo command instances are reused (e.g. in NetTxTransactionContext.Prepare()). If they are not cloned then the list will contain the second command twice and the no instance of the first command because the first command is changed after added to the list by the reassignment of some values when it is reused. This results in wrong replied messages on reconnects. Another solution is not to reuse any command instance in the whole code. -- This message was sent by Atlassian JIRA (v6.1#6144)