activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-3285) ActiveMQXAConnectionFactory does not respect various parameters for redelivery policy
Date Wed, 01 Aug 2012 14:49:04 GMT


Timothy Bish commented on AMQ-3285:

Added to /activemq-core/src/test/java/org/apache/activemq/
to show that there is no issue on client.  The test case has an incorrect option 'deliveryDelay'
which should be 'redeliveryDelay'
> ActiveMQXAConnectionFactory does not respect various parameters for redelivery policy
> -------------------------------------------------------------------------------------
>                 Key: AMQ-3285
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.4.0, 5.4.2, 5.5.0
>            Reporter: Jaskirat Bhatia
>         Attachments:,
> 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
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.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message