Attempt to Save Damage Report Results in Exception ToolMethodCommand.execute failed: tool = "com.splwg.oms.client.damage.DamageAssessment", method name = "saveDamageReport"
(Doc ID 2635466.1)
Last updated on OCTOBER 04, 2023
Applies to:
Oracle Utilities Network Management System - Version 2.4.0.1.0 and laterOracle Network Management for Utilities - DMS - Version 2.4.0.1.0 to 2.4.0.1.0 [Release 2.4]
Information in this document applies to any platform.
Symptoms
On : 2.4.0.1.0 version, Web Workspace
Unable To Save Damage Report
Trying to save a damage report produces an error message is produced 'unable to save',
ERROR
3-thread-4] ERROR com.splwg.oms.jbot.adapter.JBotAdapter: com.splwg.oms.jbot.JBotException: ToolMethodCommand.execute failed: tool = "com.splwg.oms.client.damage.DamageAssessment", method name = "saveDamageReport"
com.splwg.oms.jbot.JBotException: ToolMethodCommand.execute failed: tool = "com.splwg.oms.client.damage.DamageAssessment", method name = "saveDamageReport"
at com.splwg.oms.jbot.command.ToolMethodCommand.execute(ToolMethodCommand.java:55) ~[nms_client.jar:?]
at com.splwg.oms.jbot.JBotCommand.executeCommand(JBotCommand.java:420) ~[nms_client.jar:?]
at com.splwg.oms.jbot.CommandProcessor.processCommand(CommandProcessor.java:163) ~[nms_client.jar:?]
at com.splwg.oms.jbot.CommandProcessor.processPackage(CommandProcessor.java:284) ~[nms_client.jar:?]
at com.splwg.oms.jbot.adapter.JBotAdapter$1.run(JBotAdapter.java:671) [nms_client.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:1.8.0_231]
at java.util.concurrent.FutureTask.run(Unknown Source) [?:1.8.0_231]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_231]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_231]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_231]
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_231]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_231]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_231]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_231]
at com.splwg.oms.jbot.command.ToolMethodCommand.execute(ToolMethodCommand.java:50) ~[nms_client.jar:?]
... 9 more
Caused by: com.splwg.oms.framework.exception.OmsClientException: DAMAGE.INC_CREATE_FAIL
at com.splwg.oms.client.damage.DamageAssessment.handleServiceException(DamageAssessment.java:860) ~[nms_client.jar:?]
at com.splwg.oms.client.damage.DamageAssessment.saveDamageReport(DamageAssessment.java:502) ~[nms_client.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_231]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_231]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_231]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_231]
at com.splwg.oms.jbot.command.ToolMethodCommand.execute(ToolMethodCommand.java:50) ~[nms_client.jar:?]
... 9 more
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Select an event
2. Select to add a Damage Assessment
3. Add the necessary details and then try to Save.
Changes
This is happening after upgrading NMS release to 2.4.0.1
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 |