Scheduler Going Down With NUMBERFORMATEXCEPTION
(Doc ID 2285422.1)
Last updated on APRIL 03, 2024
Applies to:
Oracle Utilities Mobile Workforce Management - Version 2.2.0.3.13 to 2.2.0.3.13 [Release 2.2]Oracle Real-Time Scheduler - Version 2.2.0.3.13 to 2.2.0.3.13 [Release 2.2]
Information in this document applies to any platform.
Symptoms
The scheduler is going down with NumberFormatException.
The following error is observe in the logs.
ERROR
-----------------------
[SOUTH:SchedulerManager] INFO (com.splwg.mwm.support.scheduler.process.SchedulerManager) Sending SYNC_PLAN to the Scheduler
[SOUTH:SchedulerManager] ERROR (com.splwg.mwm.support.scheduler.packets.AbstractHIPPacket) Field [LOADTIME] has invalid value (4294523021)
java.lang.NumberFormatException: For input string: "4294523021"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:59)
at java.lang.Integer.parseInt(Integer.java:472)
at java.lang.Integer.parseInt(Integer.java:510)
at com.splwg.mwm.support.scheduler.packets.DurationFieldValue.strToDuration(DurationFieldValue.java:97)
at com.splwg.mwm.support.scheduler.packets.DurationFieldValue.fromHIPField(DurationFieldValue.java:41)
at com.splwg.mwm.support.scheduler.packets.AbstractHIPPacket.fromHIP(AbstractHIPPacket.java:85)
at com.splwg.mwm.support.scheduler.process.ReceivedBatchPacket.(ReceivedBatchPacket.java:53)
at com.splwg.mwm.support.scheduler.process.SchedulerEventsUpdate.receivePackets(SchedulerEventsUpdate.java:96)
at com.splwg.mwm.support.scheduler.process.SchedulerManagerCycle.processSchedulerEvents(SchedulerManagerCycle.java:277)
at com.splwg.mwm.support.scheduler.process.SchedulerManagerCycle.updateFromScheduler(SchedulerManagerCycle.java:114)
at com.splwg.mwm.support.scheduler.process.SchedulerManager.runSchedulerManager(SchedulerManager.java:368)
at com.splwg.mwm.support.scheduler.process.SchedulerManager.run(SchedulerManager.java:339)
at com.splwg.mwm.support.scheduler.common.SchedRunnableWrapper.run(SchedRunnableWrapper.java:54)
at java.lang.Thread.run(Thread.java:767)
[SOUTH:SchedulerManager] ERROR (com.splwg.mwm.support.scheduler.process.SchedulerManager) Caught exception from Scheduler Manager main loop
[SOUTH:SchedulerManager] INFO (com.splwg.mwm.support.scheduler.process.Sched
[SOUTH:SchedulerManager] ERROR (com.splwg.mwm.support.scheduler.packets.AbstractHIPPacket) Field [LOADTIME] has invalid value (4294523021)
java.lang.NumberFormatException: For input string: "4294523021"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:59)
at java.lang.Integer.parseInt(Integer.java:472)
at java.lang.Integer.parseInt(Integer.java:510)
at com.splwg.mwm.support.scheduler.packets.DurationFieldValue.strToDuration(DurationFieldValue.java:97)
at com.splwg.mwm.support.scheduler.packets.DurationFieldValue.fromHIPField(DurationFieldValue.java:41)
at com.splwg.mwm.support.scheduler.packets.AbstractHIPPacket.fromHIP(AbstractHIPPacket.java:85)
at com.splwg.mwm.support.scheduler.process.ReceivedBatchPacket.(ReceivedBatchPacket.java:53)
at com.splwg.mwm.support.scheduler.process.SchedulerEventsUpdate.receivePackets(SchedulerEventsUpdate.java:96)
at com.splwg.mwm.support.scheduler.process.SchedulerManagerCycle.processSchedulerEvents(SchedulerManagerCycle.java:277)
at com.splwg.mwm.support.scheduler.process.SchedulerManagerCycle.updateFromScheduler(SchedulerManagerCycle.java:114)
at com.splwg.mwm.support.scheduler.process.SchedulerManager.runSchedulerManager(SchedulerManager.java:368)
at com.splwg.mwm.support.scheduler.process.SchedulerManager.run(SchedulerManager.java:339)
at com.splwg.mwm.support.scheduler.common.SchedRunnableWrapper.run(SchedRunnableWrapper.java:54)
at java.lang.Thread.run(Thread.java:767)
[SOUTH:SchedulerManager] ERROR (com.splwg.mwm.support.scheduler.process.SchedulerManager) Caught exception from Scheduler Manager main loop
[SOUTH:SchedulerManager] INFO (com.splwg.mwm.support.scheduler.process.Sched
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 |