I get how it would be transactional, but why does the Transaction Service
monitor act like there's a perpetual active transaction for every time it's
invoked? Even after the app is undeployed? It's using the default timer pool.
I created an even simpler example that exhibits the same behavior: package ;
import javax.ejb.Schedule; import javax.ejb.Stateless; import
javax.ejb.Timer; @Stateless public class TimerTest {
@SuppressWarnings("unused") @Schedule(second="0", minute="*", hour="8-23",
dayOfWeek="Mon-Fri", dayOfMonth="*", month="*", year="*", info="MyTimer")
public void scheduledTimeout(final Timer t) { System.out.println("Timer2"); }
}
--
[Message sent by forum member 'hapi']
View Post: http://forums.java.net/node/891143