If the ExceptionFilter is configured (using web:exception-filter in components.xml) and a UserTransaction is not available in JNDI, then the filter bails when it calls ExceptionFilter#rollbackTransactionIfNecessary() in the finally block. Those folks who are using Seam without the transaction management must disable this filter (and lose the benefit of exception handling in Seam) because of this limitation. Is there anyway to do a check before heading into this region of code? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029409#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...