Exactly. Every situation/scecnario you have posed is not relevant *right now*. The fix from the task simply allows for a transaction timeout for MDB's being that we are directly controlling the transaction demarcation which is not interceptor/AOP based (though I have a working version of this). For the other scenarios (ActiveMQ, user inflow RARs), I am not sure this even makes sense being that 1) We have no control over this and a specialized MEF is really not applicable to ActiveMQ's implementation anyway. How exactly would this help ActiveMQ? 2) Same goes for other inbound RAR's that we do not control. How would a specialized MEF help this scenario? Do you expect them to case the MEF to a JBoss specific implementation and get the transaction timeout? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013671#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...