activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: redeliveryPlugin seems to have problems with defaultEntry
Date Tue, 02 Sep 2014 13:57:34 GMT
On 09/01/2014 03:14 AM, preben wrote:
> Good point.
>
> I deleted the whole kahadb+tmp directory and started with a clean running
> server, but the results are the same.
>
> I'm still getting the default 6 amq redeliveries and then the broker
> redelivery pluging kicks in on 7-10.
>
> 2014-09-01 09:01:10,224 | INFO  | Refreshing Root WebApplicationContext:
> startup date [Mon Sep 01 09:01:10 CEST 2014]; root of context hierarchy |
> org.springframework.web.context.support.XmlWebApplicationContext | main
> 2014-09-01 09:01:10,229 | INFO  | Loading XML bean definitions from
> ServletContext resource [/WEB-INF/webconsole-embedded.xml] |
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader | main
> 2014-09-01 09:01:10,290 | INFO  | Loading XML bean definitions from
> ServletContext resource [/WEB-INF/webconsole-query.xml] |
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader | main
> 2014-09-01 09:01:10,332 | INFO  | Loading properties file from URL
> [file:C:/java/apache-activemq-5.10.0/bin/../conf/credentials.properties] |
> org.springframework.beans.factory.config.PropertyPlaceholderConfigurer |
> main
> 2014-09-01 09:01:10,383 | INFO  | Pre-instantiating singletons in
> org.springframework.beans.factory.support.DefaultListableBeanFactory@3d925789:
> defining beans
> [queueBrowser,messageQuery,queueConsumerQuery,queueProducerQuery,topicProducerQuery,topicSubscriberQuery,connectionQuery,org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0,brokerQuery,sessionPool,connectionFactory];
> root of factory hierarchy |
> org.springframework.beans.factory.support.DefaultListableBeanFactory | main
> 2014-09-01 09:01:10,512 | INFO  | ActiveMQ WebConsole available at
> http://0.0.0.0:8161/ | org.apache.activemq.web.WebConsoleStarter | main
> 2014-09-01 09:01:10,590 | INFO  | Initializing Spring FrameworkServlet
> 'dispatcher' | /admin | main
> 2014-09-01 09:01:10,592 | INFO  | FrameworkServlet 'dispatcher':
> initialization started | org.springframework.web.servlet.DispatcherServlet |
> main
> 2014-09-01 09:01:10,609 | INFO  | Refreshing WebApplicationContext for
> namespace 'dispatcher-servlet': startup date [Mon Sep 01 09:01:10 CEST
> 2014]; parent: Root WebApplicationContext |
> org.springframework.web.context.support.XmlWebApplicationContext | main
> 2014-09-01 09:01:10,610 | INFO  | Loading XML bean definitions from
> ServletContext resource [/WEB-INF/dispatcher-servlet.xml] |
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader | main
> 2014-09-01 09:01:10,641 | INFO  | Pre-instantiating singletons in
> org.springframework.beans.factory.support.DefaultListableBeanFactory@462f59c8:
> defining beans
> [handlerMapping,/createDestination.action,/deleteDestination.action,/createSubscriber.action,/deleteSubscriber.action,/sendMessage.action,/purgeDestination.action,/deleteMessage.action,/copyMessage.action,/moveMessage.action,/deleteJob.action,exceptionResolver];
> parent:
> org.springframework.beans.factory.support.DefaultListableBeanFactory@3d925789
> | org.springframework.beans.factory.support.DefaultListableBeanFactory |
> main
> 2014-09-01 09:01:10,790 | INFO  | FrameworkServlet 'dispatcher':
> initialization completed in 189 ms |
> org.springframework.web.servlet.DispatcherServlet | main
> 2014-09-01 09:01:11,067 | INFO  | jolokia-agent: No access restrictor found
> at classpath:/jolokia-access.xml, access to all MBeans is allowed | /api |
> main
> 2014-09-01 09:02:54,797 | TRACE | redelivery #7 of:
> ID:A70103-54804-1409554907290-3:1:1:1:1 with delay: 10000, dest:
> queue://demo | org.apache.activemq.broker.util.RedeliveryPlugin | ActiveMQ
> Transport: tcp:///127.0.0.1:54805@61616
> 2014-09-01 09:03:04,142 | TRACE | redelivery #8 of:
> ID:A70103-54804-1409554907290-3:1:1:1:1 with delay: 20000, dest:
> queue://demo | org.apache.activemq.broker.util.RedeliveryPlugin | ActiveMQ
> Transport: tcp:///127.0.0.1:54805@61616
> 2014-09-01 09:03:24,082 | TRACE | redelivery #9 of:
> ID:A70103-54804-1409554907290-3:1:1:1:1 with delay: 40000, dest:
> queue://demo | org.apache.activemq.broker.util.RedeliveryPlugin | ActiveMQ
> Transport: tcp:///127.0.0.1:54805@61616
> 2014-09-01 09:04:04,099 | TRACE | redelivery #10 of:
> ID:A70103-54804-1409554907290-3:1:1:1:1 with delay: 80000, dest:
> queue://demo | org.apache.activemq.broker.util.RedeliveryPlugin | ActiveMQ
> Transport: tcp:///127.0.0.1:54805@61616
>
>
> So there seems to be 2 problems here.
> The defaultEntry is not taken into account
> The RedeliveryPlugin waits to kick in when the amq default redeliveries have
> completed.
>
> Btw I'm running the setup on a jee server using the jca adapter with broker
> connect =
> failover:(tcp://localhost:61616)?jms.rmIdFromConnectionId=true&jms.prefetchPolicy.all=1&randomize=false
>
> That seems to work ok with reconnect and all.
>
> Best,
> Preben
> This seems to work ok
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/redeliveryPlugin-seems-to-have-problems-with-defaultEntry-tp4685094p4685199.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
You need to configure your client to have zero redeliver attempts so 
that the Broker will kick in immediately, otherwise you have to wait for 
the client to perform its local max redelivery tries.

-- 
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