EJB3.1 @Schedule in clustered environment

Question

This is a follow up question to EJB3.1 Timer cancel issue

I used Spring's @Scheduled earlier in my projects. Is EJB3.1 @Schedule similar to that? How does EJB3.1 @Schedule fare in Clustered environment? In a Clustered environment where there are multiple JVMs, how can we make sure only one Scheduler/Timer is run at a time? For example I want inventory level from database emailed to a customer for every hour and I don't want duplicated emails being sent out. I know work around like setting a database flag to avoid further duplication. But, I'm not seeing this as a proper solution. Any ideas on this please?

Moonfaced

if your are using JBoss may be this can be useful. docs.jboss.org/jbossclustering/cluster_guide/5.1/html/… – Spiritism

I am exactly facing the same EJB @Schedule duplicate triggers in clustered env. How did you solve it? Thx – Urgent