I will add more logs tomorrow.
I have rewritten the timer user EJB injection and get slightly different
errors, but it might shed some more light on the problem.
It definitely looks like a class loader issue though...
I have also seen the following exception:
| 2009-02-21 21:31:36,562
Seems like the Command bean is deployed before the User bean and that the
@Timeout happens to early.
I guess the beans are deployed in alphabetical order?
Changing the name to XXXCommandBean fixed the issue...
Any ways of controlling this other than changing names of classes?
There are still
I have the following Timer service class defined:
| @Stateless
| @RemoteBinding(jndiBinding=XXXCommandRemote)
| public class XXXCommandBean implements XXXCommandRemote
| {
| static Logger logger = Logger.getLogger(XXXCommandBean.class);
|
| @Resource TimerService
Hi!
I'm setting some timers using EJB TimerService:
@Stateless
| public class CommandBean implements CommandRemote
| {
| static Logger logger = Logger.getLogger(PlayerBean.class);
|
| @Resource TimerService timerService;
|
| public void scheduleCommand(Command
