dev@glassfish.java.net

Re: [OndemandServer] EJB Service

From: Sherry Shen <Sherry.Shen_at_Sun.COM>
Date: Mon, 25 Feb 2008 22:51:45 -0800

呉傑 wrote, On 2/25/2008 10:30 PM:

> Hi Binod,
>
> Thanks for your quik and aspiring reply.
>
>>> I have the following questions about EJB Timer Service.
>>> 1, Is EJB Timer Service initialized when DAS startup or Cluster
>>> startup.
>>
>>
>> Yes. It is initialized.
>
> Excuse, I am eager to confirm the following question again.
> Is it initialized in the DAS startup process or cluster startup process?
>
> Thanks a lot.
> -Wu.
>
Thanks for the discussion. I am looking at a similar issue.

A. From DAS start up on default domain1, DAS server.log shows:
[#|2008-02-25T22:32:48.589-0800|INFO|sun-appserver9.1|
javax.enterprise.system.container.ejb|_ThreadID=17;
_ThreadName=pool-1-thread-8;jdbc/__TimerPool;|
EJB5109:EJB Timer Service started successfully for datasource
[jdbc/__TimerPool]|#]

[#|2008-02-25T22:32:48.590-0800|INFO|sun-appserver9.1|
javax.enterprise.system.core.classloading|_ThreadID=17;_ThreadName=
pool-1-thread-8;__ejb_container_timer_app;|LDR5010: All ejb(s) of
[__ejb_container_timer_app] loaded successfully!|#]


B. From a cluster startup on a created domain, the server.log in
one of the instance shows:
[#|2008-02-25T15:15:12.392-0800|WARNING|sun-appserver9.1|
javax.enterprise.system.container.ejb|_ThreadID=16;_ThreadName=
pool-1-thread-4;TimerBean;_RequestID=34f432e5-415a-4420-8862-0286c8cdc752;
|EJB5108:Unable to initialize EJB Timer Service. The likely cause is the
database has not been started or the timer database table has not been
created.|#]

[#|2008-02-25T15:15:12.449-0800|INFO|sun-appserver9.1|
javax.enterprise.system.core.classloading|_ThreadID=16;_ThreadName=
pool-1-thread-4;__ejb_container_timer_app;|LDR5010: All ejb(s) of
[__ejb_container_timer_app] loaded successfully!|#]

How to resolve "EJB5108:Unable to initialize EJB Timer Service"

Thanks!

Sherry