activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: javax.jms.InvalidClientIDException for durable subscription on broker restart
Date Mon, 11 Aug 2014 14:02:19 GMT
On 08/11/2014 09:57 AM, khandelwalanuj wrote:
> Hi,
>
> No only one application is running on the host.
>
> Yes I am using pooled connection factory. This is how my connection factory
> looks liks:
>
> 	<bean id=&quot;&lt;b>jmsFactory*"
> class="org.apache.activemq.pool.PooledConnectionFactory"
>        		destroy-method="stop">
>        		<property name="connectionFactory">
>        			<bean class="org.apache.activemq.ActiveMQConnectionFactory">
>        				<property name="brokerURL">
>        					<value>${jms.broker.url}</value>
>        				</property>
>        			</bean>
>        		</property>
>        		<property name="maxConnections" value="6" />
>       
> and my listener is using it as:
>     <bean id="listenerContainer"
>       
> class="org.springframework.jms.listener.DefaultMessageListenerContainer">
>        	     <property name=&quot;connectionFactory&quot;
> ref=&quot;&lt;b>jmsFactory*" />
>        	     <property name="destination" ref="topic_pnlCompleteTopic" />
>        	     <property name="durableSubscriptionName" value="FAGCompletion"
> />
>        	     <property name="pubSubDomain" value="true" />
>        	     <property name="subscriptionDurable"
> value="${jms.fagsListener.durable}" />
>        	     <property name="clientId" value="${jms.fagsListener.clientId}"
> />
>        	     <property name="messageListener" ref="pnlMessageListener" />
>        	     <property name="messageSelector" value="JMSType = 'FAG
> Completion'" />
>       </bean>
>
>
>
> Is there anything wrong I am doing ?
>
>
>
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/javax-jms-InvalidClientIDException-for-durable-subscription-on-broker-restart-tp4684381p4684392.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
When using the pool the calls to createConnection will create up to max 
connections before returning already existing connections, so if you 
want a durable subscription on a pooled connection type setup you must 
limit it to one connection.

-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.bish@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


Mime
View raw message