My Oracle Support Banner

Exception in Java Console Repeats Every 2 Seconds "Could not resolve beanClass method from proxy call" (Doc ID 1348929.1)

Last updated on JULY 27, 2022

Applies to:

Oracle Utilities Network Management System - Version 1.8.1.0 to 1.9.0 [Release 1.8 to 1.9]
Oracle Network Management for Utilities - DMS - Version 1.8.1.0 to 1.9.0 [Release 1.8 to 1.9]
Information in this document applies to any platform.

Symptoms

When launching any NMS web application from web start, the following exception prints every 2 seconds in the Java Console:

08-05 11:52:06,906 [Thread-5] ERROR com.splwg.oms.client.BaseEnvironmentManager: Exception caught in run(): java.lang.RuntimeException: Could not resolve beanClass method from proxy call
08-05 11:52:06,921 [Thread-5] WARN com.splwg.oms.client.BaseEnvironmentManager: Could not resolve beanClass method from proxy call
java.lang.RuntimeException: Could not resolve beanClass method from proxy call
at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:274)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:406)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
at $Proxy2.getPublishedMessages(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.splwg.oms.client.util.proxy.FaultToleranceEngine.callMethod(FaultToleranceEngine.java:56)
at com.splwg.oms.client.util.proxy.FaultToleranceContextFactory.invoke(FaultToleranceContextFactory.java:26)
at com.splwg.oms.client.util.proxy.ProxyContextFactory$ProxyInvocationHandler.invoke(ProxyContextFactory.java:121)
at $Proxy3.getPublishedMessages(Unknown Source)
at com.splwg.oms.client.BaseEnvironmentManager.getPublishedMessages(BaseEnvironmentManager.java:207)
at com.splwg.oms.client.BaseEnvironmentManager.run(BaseEnvironmentManager.java:241)
at java.lang.Thread.run(Unknown Source)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
at $Proxy2.getPublishedMessages(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.splwg.oms.client.util.proxy.FaultToleranceEngine.callMethod(FaultToleranceEngine.java:56)
at com.splwg.oms.client.util.proxy.FaultToleranceContextFactory.invoke(FaultToleranceContextFactory.java:26)
at com.splwg.oms.client.util.proxy.ProxyContextFactory$ProxyInvocationHandler.invoke(ProxyContextFactory.java:121)
at $Proxy3.getPublishedMessages(Unknown Source)
at com.splwg.oms.client.BaseEnvironmentManager.getPublishedMessages(BaseEnvironmentManager.java:207)
at com.splwg.oms.client.BaseEnvironmentManager.run(BaseEnvironmentManager.java:241)
at java.lang.Thread.run(Unknown Source)


Deleting the Java and Web Browser Cache did not resolve the issue.

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

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