Description of problem:
=======================
    If the MDB defines the "initialRedeliveryDelay" and "maximumRedeliveries" ActivationConfigProperty via annotation OR using "ejb-jar.xml" file, As well as if the "initialRedeliveryDelay" "config-property" is defined inside the <resource-adapter> section of standalone.xml then both are ignored, and it starts taking the default value of initialRedeliveryDelay for Activemq resource adapter as 1 Second see [1]

[1] http://activemq.apache.org/redelivery-policy.html



Version-Release number of selected component (if applicable):
============
JBoss EAP 6.3.0

How reproducible:
Steps to Reproduce:
1. Start ActiveMQ 5.9.0 broker. (or use Jboss A-MQ 6.1.0 which uses 5.9 activemq broker as default)

2. Get the ActiveMQ resource adapter 5.9.0 (behaviour is same in 5.8 rar as well) and deploy it on JBoss EAP 6.3

3. Edit the JBoss EAP 6.3 "resource-adapter" subsystem configuration as mentioned in the attached TestCase "standaloneAMQ.xml" file.

4. Start JBoss EAP 6.3 with the mentioned profile:
   ./standaone.sh -c standaloneAMQ.xml

5. Now deploy the MDB application attached "MDBApplication.jar" on EAP 6.3

6. Send some JMS Messages to "ActiveMQ" using the Test Client attached: "ActiveMQClient.jar"




Actual results:
===============
 - Neither the <config-property> defined in the resource-adapter section is working nor the MDB defined ActivationConfig properties.


Expected results:
===============
- The redelivery activation configuration defined in the MDB should have taken effect.
Additional info: