Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.215.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <B018F5DD0345EB4D9ADD89B0F229F4E314D0122B@fr-dl360-001.bc.corp>
References: <B018F5DD0345EB4D9ADD89B0F229F4E314D0122B@fr-dl360-001.bc.corp>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Sat, 15 Sep 2012 08:17:33 +0200
Message-ID: 
 <CAGB5yNkPq69DOWDTtp1B4H+waNeL9Qj4OdyoAVD8EBqss=oy4Q@mail.gmail.com>
Subject: Re: Intermittent delayed delivery
To: users@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The redelivery delay values seems high to me. Is this on purpose?
10800000 mills is a high value

On Fri, Sep 14, 2012 at 8:03 PM, Ken DeLong <ken.delong@babycenter.com> wro=
te:
> We are using ActiveMQ 5.5.1 as an embedded broker in our Spring 3.1.0 app=
lication. We have enabled message redelivery.  From time to time, we see me=
ssages that are sent to the queue, but are never delivered, or are delivere=
d hours later.  We've gone through the posts on using Spring's JMS Template=
 with ActiveMQ and think we have the proper settings.
>
> Our current theory is that perhaps when messages throw a RuntimeException=
, and get re-enqueued for later delivery, the consumers are not released an=
d the new messages can't be delivered.  However, we can't really gather muc=
h evidence to support this.
>
> I'm including  the configuration that we are using, in the hopes that som=
eone might spot something that we have got wrong.
>
> <amq:broker id=3D"jmsBroker" useJmx=3D"true" persistent=3D"true"
>        brokerName=3D"localhost" dataDirectory=3D"${catalina.home}/data/in=
tl2/jms"
>        start=3D"true">
>        <amq:destinationPolicy>
>               <amq:policyMap>
>                      <amq:policyEntries>
>                            <amq:policyEntry topic=3D">" producerFlowContr=
ol=3D"false" memoryLimit=3D"1mb" useCache=3D"false">
>                                   <amq:pendingSubscriberPolicy>
>                                   <amq:vmCursor />
>                                   </amq:pendingSubscriberPolicy>
>                            </amq:policyEntry>
>                            <!-- Prefetch : http://activemq.apache.org/wha=
t-is-the-prefetch-limit-for.html
>                                 Flow control: http://activemq.apache.org/=
producer-flow-control.html
>                                 Stuck messages: http://activemq.2283324.n=
4.nabble.com/Messages-stuck-in-queue-td3244342.html
>                                                 https://issues.apache.org=
/jira/browse/AMQ-2009
>                            -->
>                            <amq:policyEntry queue=3D">" producerFlowContr=
ol=3D"false" memoryLimit=3D"1mb" useCache=3D"false" queuePrefetch=3D"1">
>                                   <!-- Use VM cursor for better latency F=
or more information, see: http://activemq.apache.org/message-cursors.html
>                                          <pendingQueuePolicy> <vmQueueCur=
sor/> </pendingQueuePolicy> -->
>                            </amq:policyEntry>
>                      </amq:policyEntries>
>               </amq:policyMap>
>        </amq:destinationPolicy>
>        <amq:managementContext>
>               <amq:managementContext createConnector=3D"false" />
>        </amq:managementContext>
>        <amq:persistenceAdapter>
>               <amq:kahaDB directory=3D"${catalina.home}/data/intl2/jms/ka=
hadb"
>                      checkForCorruptJournalFiles=3D"true" checksumJournal=
Files=3D"true"
>                      forceRecoverIndex=3D"true" />
>        </amq:persistenceAdapter>
> </amq:broker>
>
> <!-- <bean id=3D"jmsConnectionFactory" class=3D"org.apache.activemq.pool.=
PooledConnectionFactory"
>        destroy-method=3D"stop"> -->
> <bean id=3D"jmsConnectionFactory" class=3D"org.springframework.jms.connec=
tion.CachingConnectionFactory">
>        <property name=3D"targetConnectionFactory">
>               <bean class=3D"org.apache.activemq.spring.ActiveMQConnectio=
nFactory">
>                      <property name=3D"brokerURL" value=3D"vm://localhost=
" />
>                      <property name=3D"redeliveryPolicy">
>                            <bean class=3D"org.apache.activemq.RedeliveryP=
olicy">
>                                   <property name=3D"maximumRedeliveries" =
   value=3D"15" />
>                                   <property name=3D"initialRedeliveryDela=
y" value=3D"10800000" />
>                                   <property name=3D"redeliveryDelay"     =
   value=3D"10800000" />
>                            </bean>
>                      </property>
>               </bean>
>        </property>
> </bean>
>
> <bean id=3D"eventServiceJmsTemplate" class=3D"org.springframework.jms.cor=
e.JmsTemplate">
>        <property name=3D"connectionFactory" ref=3D"jmsConnectionFactory" =
/>
>        <property name=3D"defaultDestination" ref=3D"destination" />
>        <property name=3D"pubSubDomain" value=3D"false" />
>        <property name=3D"deliveryPersistent" value=3D"true" />
> </bean>
>
> <bean id=3D"destination" class=3D"org.apache.activemq.command.ActiveMQQue=
ue">
>        <property name=3D"physicalName" value=3D"asynchQueue" />
> </bean>
>
> <bean id=3D"destinationResolver" class=3D"org.springframework.jms.support=
.destination.BeanFactoryDestinationResolver" />
>        <!--
>      http://activemq.apache.org/message-redelivery-and-dlq-handling.html
>      Tracing through Spring's code, it seems that it will not roll back t=
he transaction unless we set acknowledge to "transacted"
>      I tested it on integ, messages are not being redelivered with "auto"=
, but they are in "transacted" mode
>      Cache none: https://issues.apache.org/jira/browse/AMQ-2009
> -->
> <jms:listener-container connection-factory=3D"jmsConnectionFactory"
>                            acknowledge=3D"transacted"
>                            cache=3D"none"
>                            concurrency=3D"5"
>                            destination-resolver=3D"destinationResolver">
>        <jms:listener destination=3D"destination" ref=3D"asynchronousEvent=
Executor" />
> </jms:listener-container>
>
>
>
>
>
>
> -------------------------------------------------------------------------=
--------------
> Kenneth DeLong |  Director of Architecture, Chief Software Architect
> BabyCenter
> o: 415.344.7616
> ken.delong@babycenter.com<mailto:ken.delong@babycenter.com>
> Twitter: kenwdelong
> AIM: kenwdelong
> babycenter.com<http://babycenter.com/>
>
> like BabyCenter on Facebook<http://www.facebook.com/BabyCenter>
>


--=20
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen