i would like ADDING ejb3 beans. but i don't want to to remove the EJB2 beans for backward compatibility reasons. the majority of containers will be ejb2 for a while. so we need ejb2 beans. i have not focussed on ejb3 beans for now because that would imply that we have to factor out the common code. so the ejb3 simplifications would be countertackled by factoring out the common code between the ejb2 and ejb3 beans. so i'm not sure if that is worth while. anonymous wrote : If the bean is deployed with transaction-attribute required (which is the default), then the container should automatically rollback the transaction if a system exception is thrown, which will cause the JMS Server to retry the message for some configurable number of tries, and then place the message on the DLQ. | the thing i don't know is the actual configuration in the deployment descriptor. feel free to add this configuration property in the deployment descriptor if you know which one it is. anonymous wrote : | You can also catch non-system exception (e.g., an ObjectNotFoundException, InvalidStateException, etc), and invoke setRollbackOnly on the messageDrivenContext, i.e., please define non-system exception. afaik this means non-RuntimeExceptions, right ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981979#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...