NoSuchMethodError: com.splwg.oms.util.FormattedDate.<init>
(Doc ID 1523759.1)
Last updated on MARCH 24, 2025
Applies to:
Oracle Utilities Network Management System - Version 1.10.0.6 and laterOracle Network Management for Utilities - DMS - Version 1.10.0.6 and later
Information in this document applies to any platform.
Symptoms
Attempting to run custom DateFormat NMS commands results in the following error:
java.lang.NoSuchMethodError: com.splwg.oms.util.FormattedDate.(JLjava/text/DateFormat;)V
at com.xxxxx.conditionhistory.ConditionHistoryDataRow.setTime(ConditionHistoryDataRow.java:218)
at com.xxxxx.conditionhistory.ConditionHistoryDataRow.(ConditionHistoryDataRow.java:38)
at com.xxxxx.conditionhistory.ConditionHistoryDataStore.setDataObject(ConditionHistoryDataStore.java:39)
at com.xxxxx.conditionhistory.PopulateConditionHistoryCommand.execute(PopulateConditionHistoryCommand.java:68)
at com.splwg.oms.jbot.JBotCommand.executeCommand(JBotCommand.java:334)
at com.splwg.oms.jbot.CommandProcessor.processCommand(CommandProcessor.java:135)
at com.splwg.oms.jbot.CommandProcessor.processPackage(CommandProcessor.java:226)
at com.splwg.oms.jbot.adapter.JBotAdapter$1.run(JBotAdapter.java:635)
at com.splwg.oms.jbot.adapter.JBotAdapter.processCommands(JBotAdapter.java:643)
at com.splwg.oms.jbot.command.ExecuteActionCommand.execute(ExecuteActionCommand.java:85)
at com.splwg.oms.jbot.JBotCommand.executeCommand(JBotCommand.java:334)
at com.splwg.oms.jbot.CommandProcessor.processCommand(CommandProcessor.java:135)
at com.splwg.oms.jbot.CommandProcessor.processPackage(CommandProcessor.java:226)
at com.splwg.oms.jbot.adapter.JBotAdapter$1.run(JBotAdapter.java:635)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at com.xxxxx.conditionhistory.ConditionHistoryDataRow.setTime(ConditionHistoryDataRow.java:218)
at com.xxxxx.conditionhistory.ConditionHistoryDataRow.(ConditionHistoryDataRow.java:38)
at com.xxxxx.conditionhistory.ConditionHistoryDataStore.setDataObject(ConditionHistoryDataStore.java:39)
at com.xxxxx.conditionhistory.PopulateConditionHistoryCommand.execute(PopulateConditionHistoryCommand.java:68)
at com.splwg.oms.jbot.JBotCommand.executeCommand(JBotCommand.java:334)
at com.splwg.oms.jbot.CommandProcessor.processCommand(CommandProcessor.java:135)
at com.splwg.oms.jbot.CommandProcessor.processPackage(CommandProcessor.java:226)
at com.splwg.oms.jbot.adapter.JBotAdapter$1.run(JBotAdapter.java:635)
at com.splwg.oms.jbot.adapter.JBotAdapter.processCommands(JBotAdapter.java:643)
at com.splwg.oms.jbot.command.ExecuteActionCommand.execute(ExecuteActionCommand.java:85)
at com.splwg.oms.jbot.JBotCommand.executeCommand(JBotCommand.java:334)
at com.splwg.oms.jbot.CommandProcessor.processCommand(CommandProcessor.java:135)
at com.splwg.oms.jbot.CommandProcessor.processPackage(CommandProcessor.java:226)
at com.splwg.oms.jbot.adapter.JBotAdapter$1.run(JBotAdapter.java:635)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
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 |