Viewer Unloading and Errors in Client Log after Setting up New Application Server

(Doc ID 2324721.1)

Last updated on NOVEMBER 07, 2017

Applies to:

Oracle Utilities Network Management System - Version 1.12.0.3 and later
Oracle Network Management for Utilities - DMS - Version 1.12.0.3 and later
Information in this document applies to any platform.

Symptoms

After setting up another Application Server for NMS clients are having issues with the viewer unloading and there are exception in their client log.

ERROR

2017-10-31 07:40:49,305 AWT-EventQueue-1 WARN com.splwg.oms.jbot.JBotTool: Forcing 1.SwmanPlannedTool to embedded.
2017-10-31 07:40:50,272 AWT-EventQueue-1 WARN com.splwg.oms.jbot.JBotTool: Forcing 2.SwmanEmergencyTool to embedded.
2017-10-31 07:40:55,794 Thread-7 WARN com.splwg.oms.client.BaseEnvironmentManager: Connection to app server was reset.
2017-10-31 07:40:55,903 Thread-7 INFO com.splwg.oms.common.intersys.hlm.BaseMessageHelper: Resetting jms queue
2017-10-31 07:40:56,855 AWT-EventQueue-1 INFO com.splwg.oms.client.viewer.ViewerPanel: ViewerPanel.getStringProperty: property viewer.condition_flash_color not found
weblogic.jms.common.AlreadyClosedException: JMSClientExceptions:055094The producer is closed.
at weblogic.jms.client.JMSProducer.checkClosed(JMSProducer.java:1106)
at weblogic.jms.client.JMSProducer.publicCheckClosed(JMSProducer.java:1114)
at weblogic.jms.client.ReconnectController.checkClosedReconnect(ReconnectController.java:678)
at weblogic.jms.client.WLProducerImpl.checkClosedReconnectGetProducer(WLProducerImpl.java:57)
at weblogic.jms.client.WLProducerImpl.checkClosedReconnectGetProducer(WLProducerImpl.java:60)
at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:966)
at com.splwg.oms.common.intersys.hlm.BaseMessageHelper.updateListeningToolList(BaseMessageHelper.java:185)
at com.splwg.oms.common.intersys.hlm.BaseMessageHelper.refresh(BaseMessageHelper.java:350)
at com.splwg.oms.common.intersys.hlm.BaseMessageHelper.toolEventHandler(BaseMessageHelper.java:124)
at com.splwg.oms.client.BaseEnvironmentManager.processMessage(BaseEnvironmentManager.java:545)
at com.splwg.oms.client.BaseEnvironmentManager.run(BaseEnvironmentManager.java:276)
at java.lang.Thread.run(Unknown Source)
2017-10-31 07:40:57,417 AWT-EventQueue-1 WARN com.splwg.oms.client.util.symbol.VectorSymbolFactory: Symbol 6002 not found, Setting to BlankSymbol
2017-10-31 07:40:57,417 AWT-EventQueue-1 WARN com.splwg.oms.client.util.symbol.VectorSymbolFactory: Symbol 6003 not found, Setting to BlankSymbol
2017-10-31 07:43:11,840 Thread-7 WARN com.splwg.oms.client.BaseEnvironmentManager: Connection to app server was reset.

Changes

An additional application server was setup, so there are now two running.

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