Non of the deploy/undeploy/restart operations can make the Timer Service
null in the middle of the execution. If the Timer Service wasn't
started, it wouldn't have allowed the application that uses timers to
start either. So something happened to the Timer Service, so it became
null during the run. If server restart doesn't help, it means that this
condition happens every time. There should be errors in the server.log
when this happens.
-marina
forums_at_java.net wrote:
> It is possibile that some deploy or undeploy or server restart occurs
> when
> timers are working.
>
> I'm not sure, but it is possibile!
>
> Now, how can I reset this error (without re-install glassfish) and can
> work
> fine with ejb timer?
>
> I try to change the connection pool from my mysql connection pool to
> derby
> default connection pool, but nothing.
>
>
> --
>
> [Message sent by forum member 'peppeme']
>
> View Post: http://forums.java.net/node/884495
>
>