Poor Error Handling On Filter Menu Cauases Application to Get Into a Invalid State (Doc ID 2252635.1)

Last updated on APRIL 12, 2017

Applies to:

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

Symptoms

On : NMS 1.12.0.3

Poor error handling on filter menus.

If a user enters something that is not expected as a Match Value and applies the filter, this can cause an exception.  This also puts the application into a state where the users must log out in  order to clear the problem.

2017-03-31 09:09:08,804 [AWT-EventQueue-1] WARN com.splwg.oms.jbot.FilterItem: Could not convert to class java.lang.Integer
Exception in thread "AWT-EventQueue-1" com.splwg.oms.framework.exception.OmsRuntimeException: CAST_EXCEPTION_INTEGER
at com.splwg.oms.util.ObjectComparator.compareToIgnoreCase(ObjectComparator.java:136)
at com.splwg.oms.jbot.FilterItem.matches(FilterItem.java:244)
at com.splwg.oms.jbot.FilterCustomDataStoreDecorator.wouldBeFilteredOut(FilterCustomDataStoreDecorator.java:70)
at com.splwg.oms.jbot.FilterDataStoreDecorator.checkWouldBeFilteredOut(FilterDataStoreDecorator.java:93)
at com.splwg.oms.jbot.FilterCustomDataStoreDecorator.filter(FilterCustomDataStoreDecorator.java:98)
at com.splwg.oms.jbot.FilterDataStoreDecorator.computeMapping(FilterDataStoreDecorator.java:47)
at com.splwg.oms.jbot.AbstractDataStoreDecorator.validateMapping(AbstractDataStoreDecorator.java:786)
at com.splwg.oms.jbot.AbstractDataStoreDecorator.getNext(AbstractDataStoreDecorator.java:230)
at com.splwg.oms.jbot.AbstractDataStoreDecorator.getDataRowCount(AbstractDataStoreDecorator.java:401)
at com.splwg.oms.jbot.AbstractDataStoreDecorator.initializeMapping(AbstractDataStoreDecorator.java:139)
at com.splwg.oms.jbot.SortDataStoreDecorator.computeMapping(SortDataStoreDecorator.java:60)
at com.splwg.oms.jbot.AbstractDataStoreDecorator.validateMapping(AbstractDataStoreDecorator.java:786)
at com.splwg.oms.jbot.AbstractDataStoreDecorator.getNext(AbstractDataStoreDecorator.java:230)
at com.splwg.oms.jbot.AbstractDataStoreDecorator.getDataRowCount(AbstractDataStoreDecorator.java:401)
at com.splwg.oms.jbot.JBotTableModel.getRowCount(JBotTableModel.java:159)
...
Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer
at java.lang.Integer.compareTo(Unknown Source)
at com.splwg.oms.util.ObjectComparator.compareToIgnoreCase(ObjectComparator.java:98)
... 55 more

 


The issue can be reproduced with the following steps:
1. Attempt to add a formula in the Match Value side of the filter menu (changing the operator to >=, and putting (1+1) in the Match Value field), you get told that what you entered is not a valid integer.
2. When you okay it, if you attempt to 'Exit', you get told that '''' is not a valid integer and the operator that you had entered gets restored to 'any'.
3. Now the form appears to be what you started with, but attempting to Exit still gives the same error message, and using the 'X' to close the window, fails to close the window properly.

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