Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of gary.tully@gmail.com designates
 209.85.216.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=bV5XnqsEHw7ht8QCdYoUc65BG2y8+Ab/02Fj7t2My7NQEbKS5aDsEsCjfxZmbXxaAi
         aD1l7XEQKKr49yxa9R8svDgqmOKFgmMThpP9kraLqAshNMos2wijgQDHMAyBNkyrfqMK
         Z0HYZs2/fshD5YvCAuYS9hkWBOuD/5vXkfx7Y=
MIME-Version: 1.0
In-Reply-To: <1294786384663-3209848.post@n4.nabble.com>
References: <1294786384663-3209848.post@n4.nabble.com>
Date: Thu, 13 Jan 2011 11:10:14 +0000
Message-ID: <AANLkTikm7qG7SoXsoAOwZ=uQ51BYVzKgPBomPkGSMGqW@mail.gmail.com>
Subject: Re: durable topic subscriber using spring and atomikos
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

You cannot use a connection pool if you are setting the client Id on a
connection factory because a durable sub can only be active on a
single connection at a time.

A durable subscription is tied to a well known clientId and
subscriptionName, message are stored based on this identity and it
needs to be unique so that the ordering and delivery can be
guaranteed.

It is possible to configure the container to specify the clientId on
an individual connection basis such that you don't set it on the
factory?

What is your use case for using a durable subscription and a connection poo=
l.

Some more detail in an answer from a while back:
http://osdir.com/ml/java.activemq.user/2005-05/msg00141.html


On 11 January 2011 22:53, softweave <janee@softweave.com> wrote:
>
> I wrote a topic listener that works fine as a non-durable topic subscribe=
r. I
> want to convert it to a durable topic subscriber, but am running into
> problems.
>
> This portion of the spring configuration sets up the topic listener:
>
> =A0 =A0 =A0 =A0<bean id=3D"xaFactory"
> class=3D"org.apache.activemq.ActiveMQXAConnectionFactory">
> =A0 =A0 =A0 =A0<property name=3D"brokerURL" value=3D"tcp://localhost:6161=
6"/>
> <!-- =A0 =A0 <property name=3D"clientID" value=3D"xaEventListenerConnecti=
on" />-->
> =A0 =A0 =A0 =A0</bean>
>
> =A0 =A0 =A0 =A0<bean id=3D"atomikosConnectionFactoryBean"
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0class=3D"com.atomikos.jms.AtomikosConnecti=
onFactoryBean"
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0init-method=3D"init" destroy-method=3D"clo=
se">
> =A0 =A0 =A0 =A0 =A0<property name=3D"uniqueResourceName" value=3D"ACTIVEM=
Q_BROKER"/>
> =A0 =A0 =A0 =A0 =A0<property name=3D"xaConnectionFactory" ref=3D"xaFactor=
y" />
> =A0 =A0 =A0 =A0 =A0<property name=3D"maxPoolSize" value=3D"1"/>
> =A0 =A0 =A0 =A0</bean>
>
> =A0 =A0 =A0 =A0<bean id=3D"eventHandler" class=3D"com.med.XAEventHandler"=
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<property name=3D"eventRepository" ref=3D"=
eventRepository"/>
> =A0 =A0 =A0 =A0</bean>
>
> =A0 =A0 =A0 =A0<!-- a class that implements javax.jms.MessageListener -->
> =A0 =A0 =A0 =A0<bean id=3D"eventListener" class=3D"com.med.XAEventListene=
r">
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<property name=3D"eventHandler" ref=3D"eve=
ntHandler"/>
> =A0 =A0 =A0 =A0</bean>
>
> =A0 =A0 =A0 =A0<!-- =A0initialize the destination -->
> =A0 =A0<bean id=3D"eventTopic" class=3D"org.apache.activemq.command.Activ=
eMQTopic"
>>
> =A0 =A0 =A0 =A0 =A0<constructor-arg value=3D"ChangeDataEvents.Topic" />
> =A0 =A0</bean>
>
> =A0 =A0 =A0 =A0<!-- Configure the session pool for JMS.
> =A0 =A0 =A0 =A0This will also manage the transactions for incoming messag=
es. -->
> =A0 =A0 =A0 =A0<bean id=3D"eventListenerContainer"
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0class=3D"com.atomikos.jms.extra.MessageDri=
venContainer"
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0init-method=3D"start" destroy-method=3D"st=
op">
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<property name=3D"atomikosConnectionFactor=
yBean"
> ref=3D"atomikosConnectionFactoryBean" />
> =A0 =A0 =A0 =A0 =A0 =A0<property
> name=3D"transactionTimeout"><value>120</value></property>
> =A0 =A0 =A0 =A0 =A0 =A0<property name=3D"destination"><ref bean=3D"eventT=
opic"/></property>
> =A0 =A0 =A0 =A0 =A0 =A0<property name=3D"messageListener"><ref
> bean=3D"eventListener"/></property>
> =A0 =A0 =A0 =A0<property name=3D"noLocal" value=3D"true"/>
> =A0 =A0 =A0 =A0<property name=3D"poolSize" value=3D"50"/>
> <!-- =A0 =A0 <property name=3D"subscriberName" value=3D"xaEventListener"/=
>-->
> =A0 =A0 =A0 =A0</bean>
>
> If I uncomment out the clientID and subscriberName properties, it gets th=
e
> following error:
>
> WARN-[2011-01-07 22:39:20,262][Thread-5][Error delegating 'start' call to
> JMS driver
> javax.jms.InvalidClientIDException: Broker: localhost - Client:
> xaEventListenerConnection already connected from /127.0.0.1:2299
> =A0 =A0 =A0 =A0at
> org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker=
.java:243)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:8=
5)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.=
java:78)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:8=
5)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:8=
5)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBroke=
rFilter.java:91)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.broker.TransportConnection.processAddConnection(Trans=
portConnection.java:696)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConne=
ction(ManagedTransportConnection.java:83)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:137)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.broker.TransportConnection.service(TransportConnectio=
n.java:311)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConne=
ction.java:185)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.j=
ava:69)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNe=
gotiator.java:113)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonit=
or.java:228)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport=
.java:83)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:22=
0)
> =A0 =A0 =A0 =A0at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:202)
> =A0 =A0 =A0 =A0at java.lang.Thread.run(Unknown Source)
> ][-atomikos][com.atomikos.diagnostics.Slf4jConsole.println(Slf4jConsole.j=
ava:107)]
> WARN-[2011-01-07 22:39:20,278][Thread-5][MessageConsumerSession: Error in
> JMS thread
>
> How do I prevent this?
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/durab=
le-topic-subscriber-using-spring-and-atomikos-tp3209848p3209848.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


--=20
http://blog.garytully.com
http://fusesource.com