My Oracle Support Banner

Scheduler Registry Error citing TimeInterval has non-zero millisecond value 1 (Doc ID 2453957.1)

Last updated on MARCH 08, 2019

Applies to:

Oracle Utilities Mobile Workforce Management - Version 2.3.0.2.0 and later
Oracle Real-Time Scheduler - Version 2.3.0.2.0 and later
Information in this document applies to any platform.

Symptoms

The scheduler fails with the follow error. There are multiple Field Activities (FAs) which fail in the batch scheduler TPW logs.

ERROR
-----------------------
[SCHED:SchedulerRead (TASK:13255502796252)] ERROR (api.datatypes.TimeInterval) TimeInterval has non-zero millisecond value 1. Unable to get interval as seconds without loss of precision.
com.splwg.shared.common.LoggedException: TimeInterval has non-zero millisecond value 1. Unable to get interval as seconds without loss of precision.
at com.splwg.shared.common.LoggedException.raised(LoggedException.java:67) [spl-shared-4.3.0.4.0.jar:?]
at com.splwg.base.api.datatypes.TimeInterval.getAsSeconds(TimeInterval.java:104) [spl-base-4.3.0.4.0.jar:?]
at com.splwg.mwm.domain.serviceManagement.task.SchedulerReadTaskHelper.populateStwGroup(SchedulerReadTaskHelper.java:566) [spl-mwm-2.3.0.2.0.jar:?]
at com.splwg.mwm.domain.serviceManagement.task.SchedulerReadTaskHelper.populateTimeWindows(SchedulerReadTaskHelper.java:507) [spl-mwm-2.3.0.2.0.jar:?]
at com.splwg.mwm.domain.serviceManagement.task.SchedulerReadActivityAlgComp_Impl.populateTaskReadData(SchedulerReadActivityAlgComp_Impl.java:641) [spl-mwm-2.3.0.2.0.jar:?]


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, Scheduler registry error and those FAs won't dispatch.

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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.