The messaging-service.xml => <attribute name="DefaultMaxDeliveryAttempts">10</attribute> will be the configuration.
But if your app handle the failure you should return without an Exception to commit the transaction (you create the outbound message).
If you set the MaxDeliveryAttemts to '0' the message is moved to the DLQ (DeadLetterQueue).
Another nice option is to use your own DLQ configuration, in this case JBoss will move the message to your oubound queue, but this is only possible if the payload of the message should not modified.
Thanks for the reply.
It seems as though this configuration is not seen by our mq processes. We have experienced that the redelivery happens more than 10 times. It seems as though it is infinite or until the queue cannot process anymore messages.
Could you attach the messaging / queue configuration?
Also I prefere JBoss 5.1 because of some problems and different hints from other people ;-)
So why you use 5.0, any reason or are you able to migrate?
Attached are the message-service.xml and the wsmq-ds.xml configuration files. I hope these are the files that you were asking for.
When the team lead was researching JBoss after the migration was approved, it was at that time that the decision to go to 5.0 was made. We have since patched up to 5.0.1, but being that the we have moved all projects to production servers under JBoss 5.0.1 the chances of us upgrading to 5.1 is slim to nil. There is just a lot of politics involved in doing that kind of upgrade.