It should work with JBM.
You can do a simple test with the 'queue' example in JBM distro and see if it works.
Ask MDB/JCA forum for any MDB configurations that may supersede this param.
MDB's handle there own delivery. I think there is an activation property you can set. MDb's are notp art of messaging so the guys on the JCA forums or AS forums would be able to help. Or you could take a look at the AS docs.
But, when message delivering files (Ejb3 MDB), after only 5 (not 13 as expected), I got message:
This is the expected behavior. The MaxDeliveryAttempts defined at the destination gets overridden by the ActivationConfigParameters defined at your MDB. If you haven't specified this on your MDB, it uses the default value, which is 5.
Even though you could override MaxDeliveryAttempts in your MDB configuration, it can't exceed the MaxDeliveryAttempts defined at the given destination. ;-)