The timerservice? Do you mean the jmx timer or the ejb timer?
The jmx timer is in 3.2
The ejb timer is part of ejb2.1 and won't be backported to 3.2
which will always stay at ejb2.0
Thanks for the fast response.
I mean the EJB 2.1 TimerService.
If it wont be backported to 3.2.2, then i will try to use 4.0. Btw., am i doing anything wrong, is the failure described an error known to the current DR2? If not, it would be very fine if i could get some advice to find the reason for the error.
When can i expect a new DR? In the roadmap, it was projected to september, i think.
The JMS problem has already been fixed.
The 4.0DR2 code has been rolled back 3.2, the EJB Timer
and MDB code was one example of experimental code
that we need to rollback.
The problem with the timer you are testing is that it does not
work in a clustered environment.
Adrian, can you please explain how to rollback the code?
We are trying to use new JCA in 4.0 and apparantly nothing works due to JMS problems, described above.
The example source code (i.e. chapter 6, example 2) gives the very same exeption
We have already rolled back JBossMQ to the stable 3.2 code
in 4.0 - We have also rolled back the JCA1.5 changes.
I still need to go through that code to check what is stable
and what needs fixing before reapplying it.
You could try replacing the 4.0 jbossmq.jar with the 3.2 version,
I can't guarantee it will work?