Why activemq-rar-5.9.0.redhat-610379.rar does not respect InitialRedeliveryDelay when MaximumRedeliveries is defined
Issue
- While testing the resource adapter configurations it looks like
"initialRedeliveryDelay"is not working as expected when only"initialRedeliveryDelay"and"maximumRedeliveries"are defined (when specified instandalone.xmlor MDBactivationConfig). Why is that happening ? - Why this behaviour is not reproducible with
"activemq-rar-5.8.0.redhat-60024"? - We have configuration problems/questions using AM-Q and using a MDB consuming messages running on JBoss EAP-6.3. The AM-Q instance is running in it's own process (not embedded in JBoss). A resource adapter for AM-Q is deployed on JBoss and used by the MDB.
-
If more than one connection-definition (ConnectionFactory) are defined (in
standalone.xml) for the resource adapter then which one will be used by the MDB? Is it possible to define which
connection-definition to use? -
I've tried to configure the connection-definition. For example with the following:
<config-property name="MaximumRedeliveries">
3
</config-property>
<config-property name="InitialRedeliveryDelay">
1000
</config-property>
<config-property name="RedeliveryUseExponentialBackOff">
true
</config-property>
<config-property name="RedeliveryBackOffMultiplier">
5
</config-property>
- But the configuration does not take effect. How/where shall these configuration parameters be specified to take effect? There are a number of ways to specify/override configuration parameters. In which order are they prioritized? Is the client (resource adapter) doing any "local retries" (NOT going back to the AM-Q server instance)?
Environment
- Red Hat JBoss A-MQ
- 6.1.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
