Return-Path: 
 <users-return-23407-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: (qmail 2621 invoked from network); 23 Apr 2010 17:11:45 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 23 Apr 2010 17:11:45 -0000
Received: (qmail 86777 invoked by uid 500); 23 Apr 2010 17:11:45 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 86688 invoked by uid 500); 23 Apr 2010 17:11:45 -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 86679 invoked by uid 99); 23 Apr 2010 17:11:45 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Apr 2010 17:11:45 +0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.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, 23 Apr 2010 17:11:38 +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 1O5MPN-0005cW-12
	for users@activemq.apache.org; Fri, 23 Apr 2010 10:11:17 -0700
Message-ID: <28344039.post@talk.nabble.com>
Date: Fri, 23 Apr 2010 10:11:17 -0700 (PDT)
From: dnn <Daniel.Nawrocki@ngc.com>
To: users@activemq.apache.org
Subject: Re: QueueBrowser in XA Transaction?
In-Reply-To: <o2x3a73c17c1004230859m8f315b81l4cab96a844a02eb7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: Daniel.Nawrocki@ngc.com
References: <28341411.post@talk.nabble.com>
 <g2x3a73c17c1004230711i359da24fy9bf32466996423bb@mail.gmail.com>
 <28342060.post@talk.nabble.com>
 <o2x3a73c17c1004230859m8f315b81l4cab96a844a02eb7@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org



Gary Tully wrote:
> 
> Ah, ok, so that exception is the only way you know that it is not
> working...
> an XASession is transacted so it does require an active XA transaction.
> 
> Best post your entire spring context and maybe post to camel-users who
> will
> be more familiar with the <transacted> tag
> 

I get the first exception when in the destroyConsumer() method, but I am
getting another exception that causes the enumeration.getNextElement() to
return null.  I've documented both of them and included a unit test at
https://issues.apache.org/activemq/browse/AMQ-2712.  I basically copied the
existing JmsQueueBrowserTest, made all the sessions transacted, and added a
test case where no messages are added to the queue.  If I made an error
setting up the transacted sessions, let me know and I can update the unit
test.  I'm not too familiar with the core AMQ API as I have been using JMS.

My Spring setup is:

   <amq:broker id="amqBroker" useJmx="true" start="false"
useJmsPriority="true">
      <!-- pretty standard stuff goes here, has been truncated -->
   </amq:broker>

   <bean id="jmsConnectionFactory"
         class="bitronix.tm.resource.jms.PoolingConnectionFactory"
         destroy-method="close"
         depends-on="amqBroker"
   >
      <property name="uniqueName" value="activemq-xa" />
      <property name="className"
value="org.apache.activemq.ActiveMQXAConnectionFactory" />
      <property name="maxPoolSize" value="1000" />
      <property name="driverProperties">
         <props>
            <prop key="brokerURL">vm://localhost?create=false</prop>
         </props>
      </property>
   </bean>

   <!-- Spring JMS template -->
   <bean id="jmsTemplate" class="org.springframework.jms.core.JmsTemplate">
      <property name="connectionFactory" ref="jmsConnectionFactory" />
      <property name="sessionTransacted" value="true" />
   </bean>

Going forward, I will simply use a non-XA connection for the QueueBrowser. 
I'll have to manually handle the scenario where another transaction owned by
another process/thread consumes a message after I've browsed it.
-- 
View this message in context: http://old.nabble.com/QueueBrowser-in-XA-Transaction--tp28341411p28344039.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.