WARNING: Assertion << Setting Reference-time At BATCH_OFF >> Failed In Rcv_Flags.c At Line 1355
(Doc ID 2626820.1)
Last updated on OCTOBER 13, 2022
Applies to:
Oracle Utilities Mobile Workforce Management - Version 2.3.0.1.0 and laterOracle Real-Time Scheduler - Version 2.3.0.1.0 and later
Information in this document applies to any platform.
Symptoms
One of the 3 schedulers is stopping with the following warning:
WARNING: assertion << Setting reference-time at BATCH_OFF >> failed in rcv_Flags.c at line 1355
SCH (MAIN) 24/06/19 19:36:02.337 [00:00:13.790] WARNING: assertion << Setting reference-time at BATCH_OFF >> failed in rcv_Flags.c at line 1355
SCH (MAIN) 24/06/19 19:36:02.337 [00:00:13.790] TIME_LOGGING started
SCH (MAIN) 24/06/19 19:36:02.337 [00:00:13.790] MEM_LOGGING (start) total memory allocated = 228.498 mb, highWater memory = 252.046 mb
SCH (MAIN) 24/06/19 19:36:02.337 [00:00:13.790] MEM_LOGGING (finished) total memory allocated = 228.498 mb (diff = 0 mb), highWater memory = 252.046 mb
(diff = 0 mb)
SCH (MAIN) 24/06/19 19:36:02.337 [00:00:13.790] TIME_LOGGING finished and took 0 msecs cpu
SCH (MAIN) 24/06/19 19:36:02.338 [00:00:13.790] Starting Internal Event < OptimizeTours_Ext >.
SCH (MAIN) 24/06/19 19:36:02.338 [00:00:13.790] Finishing Internal Event < OptimizeTours_Ext >.
SCH (MAIN) 24/06/19 19:36:02.338 [00:00:13.790] TIME_LOGGING finished and took 3980 msecs cpu
SCH (MAIN) 24/06/19 19:36:02.337 [00:00:13.790] TIME_LOGGING started
SCH (MAIN) 24/06/19 19:36:02.337 [00:00:13.790] MEM_LOGGING (start) total memory allocated = 228.498 mb, highWater memory = 252.046 mb
SCH (MAIN) 24/06/19 19:36:02.337 [00:00:13.790] MEM_LOGGING (finished) total memory allocated = 228.498 mb (diff = 0 mb), highWater memory = 252.046 mb
(diff = 0 mb)
SCH (MAIN) 24/06/19 19:36:02.337 [00:00:13.790] TIME_LOGGING finished and took 0 msecs cpu
SCH (MAIN) 24/06/19 19:36:02.338 [00:00:13.790] Starting Internal Event < OptimizeTours_Ext >.
SCH (MAIN) 24/06/19 19:36:02.338 [00:00:13.790] Finishing Internal Event < OptimizeTours_Ext >.
SCH (MAIN) 24/06/19 19:36:02.338 [00:00:13.790] TIME_LOGGING finished and took 3980 msecs cpu
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |