Hi All,
[2011-12-21 09:56:14,043] INFO
{org.wso2.carbon.event.core.internal.builder.EventBrokerHandler} -
Successfully registered the event broker
[2011-12-21 09:56:14,074] INFO {org.quartz.impl.StdSchedulerFactory} -
Using default implementation for ThreadExecutor
[2011-12-21 09:56:14,076] INFO {org.quartz.simpl.SimpleThreadPool} - Job
execution threads will use class loader of thread: Framework Event
Dispatcher
[2011-12-21 09:56:14,098] INFO {org.quartz.core.SchedulerSignalerImpl} -
Initialized Scheduler Signaller of type: class
org.quartz.core.SchedulerSignalerImpl
[2011-12-21 09:56:14,099] INFO {org.quartz.core.QuartzScheduler} - Quartz
Scheduler v.2.1.1 created.
[2011-12-21 09:56:14,100] INFO {org.quartz.simpl.RAMJobStore} -
RAMJobStore initialized.
[2011-12-21 09:56:14,101] 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.
[2011-12-21 09:56:14,101] INFO {org.quartz.impl.StdSchedulerFactory} -
Quartz scheduler 'DefaultQuartzScheduler' initialized from default
resource file in Quartz package: 'quartz.properties'
[2011-12-21 09:56:14,101] INFO {org.quartz.impl.StdSchedulerFactory} -
Quartz scheduler version: 2.1.1
[2011-12-21 09:56:14,102] INFO {org.quartz.core.QuartzScheduler} -
Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
The above logs messages of quartz component is a default behavior of quartz
[1]. The long message in the middle is a single log info in
the QuartzScheduler class (line 268). We can hide this, if we include a
logger entry for quartz in the log4j property file. Shall we do like that?
Thanks,
Kishanthan.
[1]
http://svn.terracotta.org/svn/quartz/trunk/quartz/src/main/java/org/quartz/core/QuartzScheduler.java
On Tue, Dec 13, 2011 at 5:07 PM, Isuru Suriarachchi <is...@wso2.com> wrote:
> Yes, the deployment synchronizer issue is no longer there.. But the quarts
> logs are still there.. We have to fix that as well. Are those system outs?
> Is there a way to hide those?
>
> Thanks,
> ~Isuru
>
> On Tue, Dec 13, 2011 at 4:53 PM, Afkham Azeez <az...@wso2.com> wrote:
>
>> This was fixed last night. Get an update of
>> components/deployment-synchronizer
>>
>> On Tue, Dec 13, 2011 at 4:48 PM, Nuwan Bandara <nu...@wso2.com> wrote:
>>
>>> Hi
>>>
>>> Am seeing following messages/errors at startup.
>>>
>>> *Message printed :*
>>>
>>> [2011-12-13 16:45:31,820] INFO {org.quartz.core.QuartzScheduler} -
>>> Quartz Scheduler v.2.1.1 created.
>>> [2011-12-13 16:45:31,821] INFO {org.quartz.simpl.RAMJobStore} -
>>> RAMJobStore initialized.
>>> [2011-12-13 16:45:31,822] 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.
>>>
>>> *Error:
>>> *[2011-12-13 16:45:43,918] ERROR
>>> {org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} -
>>> Deployment synchronization for tenant 0 failed
>>> java.lang.RuntimeException:
>>> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: A
>>> repository synchronizer has not been engaged for the file path:
>>> /home/nuwanbando/wso2/carbon-dev/trunk/carbon/products/as/modules/distribution/product/target/wso2as-4.1.0-SNAPSHOT/repository/deployment/server/
>>> at
>>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.commit(DeploymentSynchronizerServiceImpl.java:73)
>>> at
>>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.doDeploymentSynchronization(CarbonDeploymentSchedulerTask.java:93)
>>> at
>>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:61)
>>> at
>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>>> at
>>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>> at java.lang.Thread.run(Thread.java:662)
>>> Caused by:
>>> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: A
>>> repository synchronizer has not been engaged for the file path:
>>> /home/nuwanbando/wso2/carbon-dev/trunk/carbon/products/as/modules/distribution/product/target/wso2as-4.1.0-SNAPSHOT/repository/deployment/server/
>>> at
>>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.getSynchronizer(DeploymentSynchronizerServiceImpl.java:92)
>>> at
>>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.commit(DeploymentSynchronizerServiceImpl.java:69)
>>> ... 11 more
>>> [2011-12-13 16:45:58,923] ERROR
>>> {org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} -
>>> Deployment synchronization for tenant 0 failed
>>> java.lang.RuntimeException:
>>> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: A
>>> repository synchronizer has not been engaged for the file path:
>>> /home/nuwanbando/wso2/carbon-dev/trunk/carbon/products/as/modules/distribution/product/target/wso2as-4.1.0-SNAPSHOT/repository/deployment/server/
>>> at
>>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.commit(DeploymentSynchronizerServiceImpl.java:73)
>>> at
>>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.doDeploymentSynchronization(CarbonDeploymentSchedulerTask.java:93)
>>> at
>>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:61)
>>> at
>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>>> at
>>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>> at java.lang.Thread.run(Thread.java:662)
>>>
>>>
>>> --
>>> *Thanks & Regards,
>>>
>>> Nuwan Bandara
>>> Senior Software Engineer
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> http://nuwan.bandara.co
>>> *
>>> <http://www.nuwanbando.com/>
>>>
>>> _______________________________________________
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * <http://www.apache.org/>**
>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919
>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Isuru Suriarachchi
> Technical Lead & Product Manager, WSO2 Application Server
> WSO2 Inc. http://wso2.com
> email : is...@wso2.com
> blog : http://isurues.wordpress.com/
>
>
> lean . enterprise . middleware
>
>
> _______________________________________________
> 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
