Return-Path: 
 <users-return-17803-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: (qmail 53705 invoked from network); 30 Jan 2009 17:22:45 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 30 Jan 2009 17:22:45 -0000
Received: (qmail 20994 invoked by uid 500); 30 Jan 2009 17:22:44 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 20976 invoked by uid 500); 30 Jan 2009 17:22:44 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Received: (qmail 20965 invoked by uid 99); 30 Jan 2009 17:22:44 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Jan 2009 09:22:44 -0800
X-ASF-Spam-Status: No, hits=2.6 required=10.0
	tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Jan 2009 17:22:37 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1LSx4K-0003mA-Lb
	for users@activemq.apache.org; Fri, 30 Jan 2009 09:22:16 -0800
Message-ID: <21751613.post@talk.nabble.com>
Date: Fri, 30 Jan 2009 09:22:16 -0800 (PST)
From: jmychasiw <jmychasiw@gmail.com>
To: users@activemq.apache.org
Subject: DLQ and XA Connection Factory with Spring
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: jmychasiw@gmail.com
X-Virus-Checked: Checked by ClamAV on apache.org


Greetings:

The only way that I can get AMQ 5.2 to properly route an invalid message to
the DLQ is if I use a Non XA connection and set sessionTransaction=true. We
would prefer to use XA if possible.
Is there a known issue with redelivery policy and XA?

Any help would be appreciated.

Could it be an error with my configuration?
<!-- XA Pooled Connection Factory -->
<bean id="jmsConnectionFactory"
class="org.jencks.pool.PooledSpringXAConnectionFactory">
   <property name="connectionFactory">
      <bean class="org.apache.activemq.ActiveMQXAConnectionFactory">
         <property name="brokerURL"
value="failover:tcp://${jms.broker.host}:${jms.broker.port}"/>
	 <property name="redeliveryPolicy">
	    <bean class="org.apache.activemq.RedeliveryPolicy">
		<property name="initialRedeliveryDelay" value="600" />
		<property name="maximumRedeliveries" value="2" />
	    </bean>
	 </property> 
      </bean>
   </property>
   <property name="jtaTransactionManager" ref="transactionManager"/>
</bean>
-- 
View this message in context: http://www.nabble.com/DLQ-and-XA-Connection-Factory-with-Spring-tp21751613p21751613.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.