Re: [dotcms] Warnings of quartz.DotJobStore in dotCMS log in dotCMS 2.2
143 views
Skip to first unread message
Jason Tesser
Oct 24, 2012, 9:14:23 AM10/24/12
to dot...@googlegroups.com
usually just noise but something is stuck in quartz table.
Maybe this use to be part of a cluster and now is not?
Thanks,
Jason Tesser
dotCMS Director, Support Services
1-305-858-1422
On Wed, Oct 24, 2012 at 8:35 AM, <bartpl...@gmail.com> wrote:
> Hi there,
>
> in the dotCMS 2.2 log we see alot of the following loglines, can you explain
> what this is, and does it cause problems?
>
> [24/10/12 13:25:39:976 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:25:59:977 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:26:19:978 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:26:39:980 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:26:59:981 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:27:19:983 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:27:39:984 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:27:59:985 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:28:19:987 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:28:39:988 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:28:59:989 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:29:19:990 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:29:39:992 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:29:59:993 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:30:19:995 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:30:39:996 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:30:59:997 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
>
>
> thanks in advance,
>
> Bart Plasmans, ISAAC
>
> --
> You received this message because you are subscribed to the Google Groups
> "dotCMS User Group" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/dotcms/-/UXHRDccPwK8J.
> To post to this group, send email to dot...@googlegroups.com.
> To unsubscribe from this group, send email to
> dotcms+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/dotcms?hl=en.
Maybe this use to be part of a cluster and now is not?
Thanks,
Jason Tesser
dotCMS Director, Support Services
1-305-858-1422
On Wed, Oct 24, 2012 at 8:35 AM, <bartpl...@gmail.com> wrote:
> Hi there,
>
> in the dotCMS 2.2 log we see alot of the following loglines, can you explain
> what this is, and does it cause problems?
>
> [24/10/12 13:25:39:976 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:25:59:977 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:26:19:978 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:26:39:980 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:26:59:981 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:27:19:983 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:27:39:984 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:27:59:985 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:28:19:987 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:28:39:988 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:28:59:989 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:29:19:990 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:29:39:992 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:29:59:993 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:30:19:995 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:30:39:996 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 13:30:59:997 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
>
>
> thanks in advance,
>
> Bart Plasmans, ISAAC
>
> --
> You received this message because you are subscribed to the Google Groups
> "dotCMS User Group" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/dotcms/-/UXHRDccPwK8J.
> To post to this group, send email to dot...@googlegroups.com.
> To unsubscribe from this group, send email to
> dotcms+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/dotcms?hl=en.
Jason Tesser
Oct 24, 2012, 9:28:29 AM10/24/12
to dot...@googlegroups.com
should clear out then as quartz settles down. Maybe next time a job run.
On Wed, Oct 24, 2012 at 9:21 AM, <bartpl...@gmail.com> wrote:
> Hi Jason,
>
> this is still part of a cluster.
>
> greetings Bart
> https://groups.google.com/d/msg/dotcms/-/XUUVYeGBwjkJ.
On Wed, Oct 24, 2012 at 9:21 AM, <bartpl...@gmail.com> wrote:
> Hi Jason,
>
> this is still part of a cluster.
>
> greetings Bart
Jason Tesser
Oct 24, 2012, 9:58:56 AM10/24/12
to dot...@googlegroups.com
hard to say look for row locks in the qrtz_ tables. OR a server that
is marked as firing a job.
It is usually just noise.
> what exactly should we clear out?
>
> thanks,
> https://groups.google.com/d/msg/dotcms/-/Sb-PL-zsp6YJ.
is marked as firing a job.
It is usually just noise.
> what exactly should we clear out?
>
> thanks,
Jason Tesser
Oct 24, 2012, 10:42:41 AM10/24/12
to dot...@googlegroups.com
really just noise. I would ignore for now. It should go away as Quartz
catches up.
Thanks,
Jason S. Tesser
Director, Support Services
dotCMS, Inc.
T: 305.858.1422 x7003
http://twitter.com/dotCMS
www.dotcms.com
> also I see this error:
>
> [24/10/12 15:21:00:614 BST] WARN quartz.DotJobStore: This scheduler
> managing cluster: null
> java.lang.reflect.UndeclaredThrowableException
> at $Proxy74.rollback(Unknown Source)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport.rollbackConnection(JobStoreSupport.java:3503)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport.doCheckin(JobStoreSupport.java:3115)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.manage(JobStoreSupport.java:3713)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.run(JobStoreSupport.java:3749)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor1075.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.quartz.impl.jdbcjobstore.AttributeRestoringConnectionInvocationHandler.invoke(AttributeRestoringConnectionInvocationHandler.java:71)
> ... 5 more
> Caused by: java.sql.SQLException: Connection is closed.
> at
> org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.checkOpen(PoolingDataSource.java:175)
> at
> org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.rollback(PoolingDataSource.java:311)
> ... 9 more
> [24/10/12 15:22:20:623 BST] WARN quartz.DotJobStore: This scheduler
> https://groups.google.com/d/msg/dotcms/-/3OPLP90W0T4J.
catches up.
Thanks,
Jason S. Tesser
Director, Support Services
dotCMS, Inc.
T: 305.858.1422 x7003
http://twitter.com/dotCMS
www.dotcms.com
> also I see this error:
>
> [24/10/12 15:21:00:614 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 15:21:00:615 BST] WARN quartz.DotJobStore: This scheduler
> cluster. This may cause inconsistent behavior.
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 15:21:20:616 BST] WARN quartz.DotJobStore: This scheduler
> cluster. This may cause inconsistent behavior.
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 15:21:20:616 BST] WARN quartz.DotJobStore: This scheduler
> cluster. This may cause inconsistent behavior.
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 15:21:40:618 BST] WARN quartz.DotJobStore: This scheduler
> cluster. This may cause inconsistent behavior.
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 15:21:40:619 BST] WARN quartz.DotJobStore: This scheduler
> cluster. This may cause inconsistent behavior.
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 15:22:00:620 BST] WARN quartz.DotJobStore: This scheduler
> cluster. This may cause inconsistent behavior.
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 15:22:00:621 BST] WARN quartz.DotJobStore: This scheduler
> cluster. This may cause inconsistent behavior.
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 15:22:00:626 BST] ERROR quartz.DotJobStore: ClusterManager: Error
> cluster. This may cause inconsistent behavior.
> managing cluster: null
> java.lang.reflect.UndeclaredThrowableException
> at $Proxy74.rollback(Unknown Source)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport.rollbackConnection(JobStoreSupport.java:3503)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport.doCheckin(JobStoreSupport.java:3115)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.manage(JobStoreSupport.java:3713)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.run(JobStoreSupport.java:3749)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor1075.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.quartz.impl.jdbcjobstore.AttributeRestoringConnectionInvocationHandler.invoke(AttributeRestoringConnectionInvocationHandler.java:71)
> ... 5 more
> Caused by: java.sql.SQLException: Connection is closed.
> at
> org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.checkOpen(PoolingDataSource.java:175)
> at
> org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.rollback(PoolingDataSource.java:311)
> ... 9 more
> [24/10/12 15:22:20:623 BST] WARN quartz.DotJobStore: This scheduler
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 15:22:20:623 BST] WARN quartz.DotJobStore: This scheduler
> cluster. This may cause inconsistent behavior.
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 15:22:40:624 BST] WARN quartz.DotJobStore: This scheduler
> cluster. This may cause inconsistent behavior.
> instance (2) is still active but was recovered by another instance in the
> cluster. This may cause inconsistent behavior.
> [24/10/12 15:22:40:625 BST] WARN quartz.DotJobStore: This scheduler
> cluster. This may cause inconsistent behavior.
Reply all
Reply to author
Forward
0 new messages