AnsweredAssumed Answered

BG Service restart query

Question asked by CMCN1982 on Sep 17, 2015
Latest reply on Sep 21, 2015 by CMCN1982

Hi all,

 

yesterday Time Slicing failed in one of our environments and upon investigation it appears to have been caused by the bg service restarting.

I have checked with my colleagues and none of us restarted the service manually.

 

In the bg-ca.log file I see this:

 

SYS   2015-09-16 12:04:47,599 [WrapperSimpleAppMain] bgp.JobLogger (clarity:none:none:none) Tenant assigned: clarity

SYS   2015-09-16 12:04:49,238 [WrapperSimpleAppMain] niku.union (clarity:scheduler:199990658__A32DAB00-EFB7-47F4-BFE8-DE4202E9319A:none) Initializing Event Manager on server instance: bg

SYS   2015-09-16 12:04:49,263 [WrapperSimpleAppMain] niku.union (clarity:scheduler:199990658__A32DAB00-EFB7-47F4-BFE8-DE4202E9319A:none) Starting Process Engine on server instance: bg

SYS   2015-09-16 12:04:49,312 [WrapperSimpleAppMain] bpm.engine (clarity:scheduler:199990658__A32DAB00-EFB7-47F4-BFE8-DE4202E9319A:none) Process Controller for engine bg-NJROS1BBLA1065 initializing...

SYS   2015-09-16 12:04:49,313 [WrapperSimpleAppMain] bpm.engine (clarity:scheduler:199990658__A32DAB00-EFB7-47F4-BFE8-DE4202E9319A:none) Process Controller for engine bg-SERVER initialized

SYS   2015-09-16 12:04:50,755 [WrapperSimpleAppMain] niku.union (clarity:scheduler:199990658__A32DAB00-EFB7-47F4-BFE8-DE4202E9319A:none) Process Engine Name: bg-SERVER

SYS   2015-09-16 12:04:50,866 [WrapperSimpleAppMain] niku.union (clarity:process_admin:199990659__30E0247E-FB56-4518-8966-5AC7F52CB948:none) Starting Message Receiver on Event Manager

SYS   2015-09-16 12:04:50,883 [Event Interest Registration Thread] niku.union (clarity:none:none:none) Registering event interests...

SYS   2015-09-16 12:04:50,911 [Thread-7] njs.SchedulerImpl (clarity:none:none:none) Niku Job Scheduler (tenant=clarity)

SYS   2015-09-16 12:04:50,911 [Thread-7] njs.SchedulerImpl (clarity:none:none:none) Clarity 14.2.0.237 Job Scheduler bg@SERVER initializing...

SYS   2015-09-16 12:04:52,252 [Thread-7] njs.SchedulerImpl (clarity:scheduler:199990660__F41AFAAF-1A40-4E02-B886-6D9A63C134B2:none) Clarity 14.2.0.237 Job Scheduler bg@SERVER initialized

 

But the log entry just before this occurs at 11:13 and doesn't really indicate a reason for the bg service restarting.

 

WARN  2015-09-16 11:13:59,157 [Pre Condition Pipeline 0 (tenant=clarity)] com.niku (clarity:process_admin:199983659__8461943B-221F-4CDF-96E0-411FF10F76F9:none) Parameter 1: 5584000

 

There is nothing in the bg-system log

 

Is there anywhere else I can check for a reason to explain this behaviour? Or anything that can be done to avoid it happening in future?

Thanks

Outcomes