You say your schedule works, but nowhere are you specifically stating you are interacting with an @Entity that would cause the XA transaction issue. The post a few back specifically showed the actions occurring in the same transaction. The following would not work without XA support. anonymous wrote : | public void firstMethod(){ | | entyManager.persist(something); | schedule(); | } | If you only interact with EJBTimers and other session beans, then there is no problem since you only have a single resource (the one supporting EJBTimers) involved in the transaction. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139773#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...