Safety Document Phase Change Causes NullPonterException in UpdateSafetyDevicePhasesCommand when Selecting OK button

(Doc ID 2339354.1)

Last updated on JANUARY 02, 2018

Applies to:

Oracle Utilities Network Management System - Version 2.3.0.0.0 to 2.3.0.1.0 [Release 2.3]
Oracle Network Management for Utilities - DMS - Version 2.3.0.0.0 to 2.3.0.1.0 [Release 2.3]
Information in this document applies to any platform.

Symptoms

When displaying the safety document phase change dialog and immediately pressing OK without changes, there are 2 things wrong.

1.  A row is added to the Tag Points table for the device.  This is a duplicate of the row you had selected

2. A NullPointerException occurs:

2017-12-13 14:58:10,746 [AWT-EventQueue-1] ERROR com.splwg.oms.jbot.adapter.JBotAdapter:  
java.lang.NullPointerException
at com.splwg.oms.fcp.command.UpdateSafetyDevicePhasesCommand.getNewPhases(UpdateSafetyDevicePhasesCommand.java:135)
at com.splwg.oms.fcp.command.UpdateSafetyDevicePhasesCommand.execute(UpdateSafetyDevicePhasesCommand.java:105)
at com.splwg.oms.jbot.JBotCommand.executeCommand(JBotCommand.java:366)
at com.splwg.oms.jbot.CommandProcessor.processCommand(CommandProcessor.java:163)
at com.splwg.oms.jbot.CommandProcessor.processPackage(CommandProcessor.java:284)
at com.splwg.oms.jbot.adapter.JBotAdapter$1.run(JBotAdapter.java:659)
at com.splwg.oms.jbot.adapter.JBotAdapter.processCommands(JBotAdapter.java:669)
at com.splwg.oms.jbot.command.ExecuteActionCommand.execute(ExecuteActionCommand.java:105)
at com.splwg.oms.jbot.JBotCommand.executeCommand(JBotCommand.java:366)
at com.splwg.oms.jbot.CommandProcessor.processCommand(CommandProcessor.java:163)
at com.splwg.oms.jbot.CommandProcessor.access$100(CommandProcessor.java:33)
at com.splwg.oms.jbot.CommandProcessor$ProcessCommandTask.run(CommandProcessor.java:397)
at com.splwg.oms.client.util.ClientThreadPool$ContextRunnable.run(ClientThreadPool.java:160)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$500(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)



It is expected that we would not get duplicated rows.  And, the exception should not happen.


The issue can be reproduced at will with the following steps:
1. Create Hold Standalone safety document.
2. Record device T15306.
3. Select Tag Points device T15385, open the change phases dialog, press Ok without changing anything.
4. A NullPointerException dialog is shown and a third row containing device T15385 is added.

 

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms