Maximo List Archive

This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.



Cron Cluster in Maximo 7.6

From: thinktank99 (2018-01-16 12:34)

We have a separate cron cluster for our cron tasks. We are on 7.6.0.6. At times we are seeing that when we create a new cron task instance, two or at time three of the cron jvms are picking that up and creating entry with their JVM name in the taskscheduler table. The taskscheduler table ends up with 2, at time 3 entries for the same cron task instance and then the cron task instance never actions due to multiple entries of the same instance.
Has anyone come across this issue and if so how have you dealt with it?

I don't want to use the dorun and donotrun properties for this as this issue is with scheduled reports as well which run on the birt cluster and schedule reports create cron instance on the go which we wont be able to control using these properties.

Hoping to get you thoughts on this.


From: Lonnie Stone (2018-01-16 13:09)

Check the system property mxe.crontask.runonschedule. If it is set to 0, try setting it to 1 to see if that solves your issue.
Thank you
Lon Stone
mail: lonnie_s_stone@yahoo.com
twitter: @LonStone3
On Tue, Jan 16, 2018 at 7:36 AM -0500, "thinktank99@outlook.com [MAXIMO]" <MAXIMO@yahoogroups.com> wrote:



 





We have a separate cron cluster for our cron tasks. We are on 7.6.0.6. At times we are seeing that when we create a new cron task instance, two or at time three of the cron jvms are picking that up and creating entry with their JVM name in the taskscheduler table. The taskscheduler table ends up with 2, at time 3 entries for the same cron task instance and then the cron task instance never actions due to multiple entries of the same instance.
Has anyone come across this issue and if so how have you dealt with it?

I don't want to use the dorun and donotrun properties for this as this issue is with scheduled reports as well which run on the birt cluster and schedule reports create cron instance on the go which we wont be able to control using these properties.

Hoping to get you thoughts on this.