This is the next question for EJB3.1 Cancel timer response
I used Spring @Scheduled earlier in my projects. Is EJB3.1 @Schedule similar to this? How does EJB3.1 @ pay fare in a clustered environment? In a clustered environment where there are multiple JVMs, how can we guarantee that only one scheduler / timer is started at a time? For example, I want the resource level from the database to be emailed to the client every hour, and I do not want duplicate emails to be sent. I know how to work with setting a database flag to avoid further duplication. But I do not think this is the right decision. Any ideas on this?
source share