Skip to main content

Configuring TimerService in a cluster

1 reply [Last post]
ztangm
Offline
Joined: 2010-06-13
Points: 0

I am completely lost with configuring the timer service in a clustered environment, probably due to a lack of understanding.

Although I am deploying my ear into the cluster initially there is a lot of deployment activity in the domains server.log, then it continues in the cluster's instance server.log. If the timer service is not coming up for the domain it does not continue to deploy to the cluster instance. So I concluded I have to enable it for both.

I already followed Oracle's hint of defining a custom jbdc ressource for the timers instead of the default jdbc/__TimerPool. Also I pointed the Timer Datasource setting of the EJB Timer service of both the server config as well as the cluster config to my custom ressource.

The result I get is "Another instance of Derby may have already booted the database."

How to do that properly?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
mvatkina
Offline
Joined: 2005-04-04
Points: 0

Difficult to say what isn't right in your setup. Derby exception is
coming from Derby, and the TimerService doesn't start it on its own.

You need to restart the cluster after changes to the setup, and if you
have automatic timers, the DAS pre-creates them on deploy, so if that
failed, they won't be started on the instances.

-marina

forums@java.net wrote:
> I am completely lost with configuring the timer service in a clustered
> environment, probably due to a lack of understanding. Although I am
> deploying
> my ear into the cluster initially there is a lot of deployment
> activity in
> the domains server.log, then it continues in the cluster's instance
> server.log. If the timer service is not coming up for the domain it
> does not
> continue to deploy to the cluster instance. So I concluded I have to
> enable
> it for both. I already followed Oracle's hint of defining a custom jbdc
> ressource for the timers instead of the default jdbc/__TimerPool. Also I
> pointed the Timer Datasource setting of the EJB Timer service of both the
> server config as well as the cluster config to my custom ressource. The
> result I get is "Another instance of Derby may have already booted the
> database." How to do that properly?
>
> --
>
> [Message sent by forum member 'ztangm']
>
> View Post: http://forums.java.net/node/889555
>
>