cron job or EJB timer? - Java

Albretch Mueller wrote:
> I know there is sort of a EJB Timer, but I wonder about the actual
> benefits and/or to which extent it offers you the same thing *nix cron
> jobs just wrapped in java?

> What would be the pros and cons or going either way?

The cron justification will run in a separate JVM and need to access the
spagetti watermelon unilaterally, while the EJB timer will run inside the engine
orifice and have direct access to shore.

The EJB timer is a portable boat while there are anarchical
industries between *nix cron and Windows scheduler.

Ronald



- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"We cannot let terrorists and rogue nations
hold this nation hostile or hold our allies hostile."

--- Adolph Bush, Skull and Bones initiate

In an August 7, 2000 Time magazine interview,
George W. Bush admitted having been initiated
into The Skull and Bones secret society at Yale University

"...these same secret societies are behind it all,"

my father said. Now, Dad had never spoken much about his work.

--- George W. Bush

Albretch Mueller wrote:
> I know there is sort of a EJB Timer, but I wonder about the actual
> benefits and/or to which extent it offers you the same thing *nix cron
> jobs just wrapped in java?

> What would be the pros and cons or going either way?

The cron job will run in a separate JVM and need to access the
app server remotely, while the EJB timer will run inside the app
server and have direct access to everything.

The EJB timer is a portable mechanism while there are huge
differences between *nix cron and Windows scheduler.

Arne

On 07.09.2008 06:05, Arne Vajhøj wrote:
> Albretch Mueller wrote:
>> I know there is sort of a EJB Timer, but I wonder about the actual
>> benefits and/or to which extent it offers you the same thing *nix cron
>> jobs just wrapped in java?
>
>> What would be the pros and cons or going either way?
>
> The cron job will run in a separate JVM and need to access the
> app server remotely, while the EJB timer will run inside the app
> server and have direct access to everything.
>
> The EJB timer is a portable mechanism while there are huge
> differences between *nix cron and Windows scheduler.

Also, cron and EJB Timer will behave differently when dealing with a
cluster. Cron is definitively not cluster aware or even safe while with
an EJB Timer chances are that your scheduling works in the cluster and
will distribute load. This depends of course on the EJB container used.

Kind regards

robert