This content has been marked as final.
Show 2 replies
-
1. Re: Timer was not registered with Tx
phillycheese Oct 27, 2005 3:53 PM (in response to phillycheese)And what's even worse is that, the Timer doesn't fire for the next scheduled event.
-
2. Re: Timer was not registered with Tx
oglueck Nov 10, 2005 5:57 AM (in response to phillycheese)I get the same warning. I am using container managed transactions in the bean and @TransactionAttribute(TransactionAttributeType.REQUIRED) on the timeout method.