My Oracle Support Banner

Error in Multispeak AMR Log: While trying to lookup 'topic.MsgRegister' didn't find subcontext 'topic' (Doc ID 2241404.1)

Last updated on JUNE 18, 2018

Applies to:

Oracle Utilities Network Management System - 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

From node that starts this error is being created:

ERROR

2017-03-02 10:42:28,921 ERROR hlm.BaseMessageHelper:153 - javax.naming.NameNotFoundException: While trying to lookup 'topic.MsgRegister' didn't find subcontext 'topic'. Resolved ''; remaining name 'topic/MsgRegister'
java.lang.RuntimeException: javax.naming.NameNotFoundException: While trying to lookup 'topic.MsgRegister' didn't find subcontext 'topic'. Resolved ''; remaining name 'topic/MsgRegister'
at com.splwg.oms.util.EJBResource.lookupObjectNoProxy(EJBResource.java:205)
at com.splwg.oms.common.intersys.hlm.BaseMessageHelper.open(BaseMessageHelper.java:296)
at com.splwg.oms.common.intersys.hlm.BaseMessageHelper.addOMSListener(BaseMessageHelper.java:92)
at com.splwg.oms.common.intersys.hlm.BaseMessageHelper.addOMSListener(BaseMessageHelper.java:109)
at com.splwg.oms.interfaces.amr.AmrBean.start(AmrBean.java:153)

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!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.