activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Lievens (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3285) ActiveMQXAConnectionFactory does not respect various parameters for redelivery policy
Date Fri, 29 Apr 2011 06:46:03 GMT

    [ https://issues.apache.org/jira/browse/AMQ-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026882#comment-13026882
] 

Jan Lievens commented on AMQ-3285:
----------------------------------

The problem lies with the fact that a PoolingConnectionFactory is used. When using the org.springframework.jms.connection.CachingConnectionFactory
the various backoff-settings do take effect. This is most likely not fixable due to the fact
that multiple ActiveMQMessageConsumers are created and destroyed when using the PoolingConnectionFactory
while that is not the case with the CachingConnectionFactory. At least what I see is that
the prolific creation and destruction of ActiveMQMessageConsumers in conjunction with the
fact that this class is holding state (e.g. the redeliveryDelay property) between rollbacks
tends to be contradictory.
Maybe someone with a better understanding of ActiveMQMessageConsumer in relation with PoolingConnectionFactory
can shed some light on this. At least there is a workaround.

> ActiveMQXAConnectionFactory does not respect various parameters for redelivery policy
> -------------------------------------------------------------------------------------
>
>                 Key: AMQ-3285
>                 URL: https://issues.apache.org/jira/browse/AMQ-3285
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.4.0, 5.4.2, 5.5.0
>            Reporter: Jaskirat Bhatia
>         Attachments: activemq-test.zip
>
>
> I tried to add these following parameters to my redelivery policy and activeMQ is not
respecting any of them except maximumRedelivery
> <spring:bean id="redeliveryPolicy" class="org.apache.activemq.RedeliveryPolicy">
> 			<spring:property name="maximumRedeliveries" value="5"/>
> 			<spring:property name="initialRedeliveryDelay" value="5000"/>
> 						<spring:property name="redeliveryDelay" value="2000"/>
> 			<spring:property name="useExponentialBackOff" value="true"/>
> 			<spring:property name="backOffMultiplier" value="2"/>
> 		</spring:bean>
> I have attached the project which I took from https://issues.apache.org/jira/browse/AMQ-1593
and added the above parameter to my brokerURL:
> tcp://localhost:5000?jms.redeliveryPolicy.maximumRedeliveries=3&jms.redeliveryPolicy.initialRedeliveryDelay=10000&jms.redeliveryPolicy.deliveryDelay=10000&jms.redeliveryPolicy.useExponentialBackOff=true&jms.redeliveryPolicy.backOffMultiplier=2
> This test case will show you that none of the parameters like initiaRedeliveryDelay etc
will take effect, except maxRedeliveries

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message