Hi all,
I'm searching for an "best practice" answer for the following problem: I have several EJB3 TimerServices. They create "WorkerJobs" every x minutes, which were enqueued into a JMS-Queue. A MDB consumes them and executes these jobs.
That works fine.
Now, the load of this perticular JBoss is - some kind - at its limit, so I'm thinking of a second, third,... server to build up a cluster.
If I just deploy the application on a cluster (shared database; shared database for JBoss-Messaging; each node has a unique server-peer-id; ...), the TimerServices will run on each node and produce to much WorkerJobs (I just want one for every x minutes).
So, what should I do? Is there a JEE-way to handle that or a JBoss-way (cluster singleton?)?
Thank you for your help, and I apologise, that this is more general JEE question.
Carsten
