Had a quick offline chat with Anjana. Seems I misunderstood his response. So, the current solution should fix $subject.
On Wed, Feb 1, 2012 at 11:05 AM, Kishanthan Thangarajah <kishant...@wso2.com > wrote: > Hi KasunG, > > On Wed, Feb 1, 2012 at 10:31 AM, KasunG Gajasinghe <kas...@wso2.com>wrote: > >> >> >> On Wed, Feb 1, 2012 at 9:02 AM, Anjana Fernando <anj...@wso2.com> wrote: >> >>> Hi, >>> >>> Sorry for the delay, I've made quartz logs to WARN log level. This >>> change is done in trunk. Also, in AS quartz dependency is coming from data >>> services feature, which has scheduled tasks bundles with it, I'm going to >>> separate out the data services task feature and only create a data services >>> only feature, so when someone install the core data services feature, they >>> won't get the scheduled tasks, which may not be required most of the time. >>> If they want it, they can install it separately. >>> >> >> AFAIK, when logger level is INFO, it will also print WARN, and ERROR >> level logs. So, I think the said solution does not address $subject. >> > > No, I think making the quartz log level to WARN will solve the $Subject > as it will get rid of the INFO level messages. Also there is one big INFO > level message from quartz which is their default behavior and all other > messages are also INFO. So setting it to WARN level will remove those. > > Thanks, > Kishanthan. > > >> Quote: http://www.javaworld.com/jw-11-2000/jw-1122-log4j.html >> log4j encourages the use of only four priorities: ERROR, WARN, INFO and >> DEBUG, listed in decreasing order of priority. >> >> A logging request is said to be *enabled* if its priority is higher than >> or equal to the priority of its category. Otherwise, the request is said to >> be *disabled.*. A category without an assigned priority will inherit one >> from the hierarchy. >> >> >> >>> Cheers, >>> Anjana. >>> >>> >>> On Tue, Jan 31, 2012 at 10:02 PM, Supun Malinga <sup...@wso2.com> wrote: >>> >>>> 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 >>>> >>>> >>> >>> >>> -- >>> *Anjana Fernando* >>> Senior Software Engineer >>> WSO2 Inc. | http://wso2.com >>> lean . enterprise . middleware >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> *Kasun Gajasinghe* >> >> Software Engineer; WSO2 Inc.; http://wso2.com >> >> , >> *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* >> *blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org> >> >> * >> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> >> >> * >> * >> >> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > *Kishanthan Thangarajah* > Software Engineer, > WSO2, Inc. > lean.enterprise.middleware > > Mobile - +94773426635 > Blog - *http://kishanthan.wordpress.com* > Twitter - *http://twitter.com/kishanthan* > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Kasun Gajasinghe* Software Engineer; WSO2 Inc.; http://wso2.com , *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* *blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org> * twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> * *
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
