Hi Dru,
What kind of exception are you experiencing? You should be able to get the exception from within your code even
if TopLink is throwing it. The EJB TimerService will run on one of your cluster nodes. You can migrate it manually
from one node to another if you need to. That it runs on one node is per specification. The migration capability is a
handy extension. And a cluster node should not have any differences between them, that is the purpose of the
cluster, right?
Manfred.
From: Dru Devore [mailto:ddevore_at_duckhouse.us]
Sent: Friday, July 25, 2008 11:03 AM
To: users_at_glassfish.dev.java.net
Subject: RE: Keeping a timer alive
The exception thrown by toplink is picked up by the server before it gets to my code so I don't have the choice of catching the exception. So I have to configure the time in the server. Now if I have the server in a cluster how will this work? Will there be one executing at any one time managed by the container or one for each server in the cluster. If it is one running then which servers configuration is taken if there are differeneces. It would be nice if it was configurable in the web.xml, I looked and didn't see it.
So many questions.