HI,

This was said in earlier mails as well.
Anjana, any update on the matter?

thanks,

org.quartz.simpl.SimpleThreadPool} -  Job execution threads will use class
loader of thread: Framework Event Dispatcher

> [2012-01-31 21:42:41,031]  INFO {org.quartz.core.SchedulerSignalerImpl} -
> Initialized Scheduler Signaller of type: class
> org.quartz.core.SchedulerSignalerImpl
> [2012-01-31 21:42:41,032]  INFO {org.quartz.core.QuartzScheduler} -
> Quartz Scheduler v.2.1.1 created.
> [2012-01-31 21:42:41,033]  INFO {org.quartz.simpl.RAMJobStore} -
> RAMJobStore initialized.
> [2012-01-31 21:42:41,034]  INFO {org.quartz.core.QuartzScheduler} -
> Scheduler meta-data: Quartz Scheduler (v2.1.1) 'DefaultQuartzScheduler'
> with instanceId 'NON_CLUSTERED'
>   Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
>   NOT STARTED.
>   Currently in standby mode.
>   Number of jobs executed: 0
>   Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
>   Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support
> persistence. and is not clustered.
>
> [2012-01-31 21:42:41,034]  INFO {org.quartz.impl.StdSchedulerFactory} -
> Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource
> file in Quartz package: 'quartz.properties'
> [2012-01-31 21:42:41,034]  INFO {org.quartz.impl.StdSchedulerFactory} -
> Quartz scheduler version: 2.1.1
> [2012-01-31 21:42:41,034]  INFO {org.quartz.core.QuartzScheduler} -
> Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
>
> Thanks!
> Charitha
>
>
>
> Charitha Kankanamge
> cell: +94 718 359 265
> blog: http://charithaka.blogspot.com <http://wso2.com>
>
>


-- 
Supun Malinga,

Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - sup...@wso2.com <sup...@wso2.com>
mobile - 071 56 91 321
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to