WLSDM Console error on server smart dashboard

[wlcommunityusers]

Hi,

When I open WLSDM console on our critical WebLogic domain, WLSDM “Servers smart dashboard” page gives below error. I’ve pasted the screen capture and the dashboard page does not come up. What could be the reason and need urgent solution? Please see error log below.

Error Log:

``` javax.servlet.ServletException: java.lang.InstantiationError: java.lang.Number at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:391) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78) at com.wlsdm.J.G.doFilter(RRFilter.java:155) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78) at com.bea.console.internal.ParamFilter.doFilter(ParamFilter.java:38) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:32) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3683) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3649) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326) at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197) at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203) at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:71) at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2433) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2281) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2259) at weblogic.servlet.internal.ServletRequestImpl.runInternal(ServletRequestImpl.java:1691) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1651) at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:270) at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348) at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333) at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54) at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41) at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:406) at weblogic.work.ExecuteThread.run(ExecuteThread.java:346) Caused by: java.lang.InstantiationError: java.lang.Number at sun.reflect.GeneratedSerializationConstructorAccessor87.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.io.ObjectStreamClass.newInstance(ObjectStreamClass.java:1006) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1997) <[ServletContext@786234214[app:consoleapp module:console path:null spec-version:3.1]] Root cause of ServletException. java.lang.InstantiationError: java.lang.Number at sun.reflect.GeneratedSerializationConstructorAccessor87.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.io.ObjectStreamClass.newInstance(ObjectStreamClass.java:1006) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1997) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1535) Truncated. see log file for complete stacktrace >

[wlsdmsupport]

The error occurs when serverRuntime is requested …

        At javax.management.remote.rmi.RMIConnector $ RemoteMBeanServerConnection.invoke (RMIConnector.java:1020)
        At weblogic.management.jmx.MBeanServerInvocationHandler.doInvoke (MBeanServerInvocationHandler.java:562)
        At weblogic.management.jmx.MBeanServerInvocationHandler.invoke (MBeanServerInvocationHandler.java:391)
        At com.sun.proxy. $ Proxy273.lookupServerRuntime (Unknown Source)
        At com.wlsdm.L.a.getServerRuntimeMBean (MBSConnection.java:475)
        At com.wlsdm.frontend.provider.GA.getServerHealthState (PerformanceHealthDatas.java:123)
        At com.wlsdm.J.O. £ (Data.java:6914)

The WLSDM serverRuntime object is requested via the weblogic console API, and the admin console is also calling managedServers for RMI.

→ Is there any problem on the WebLogic admin console > Servers page? (Just want to diagnose problem)
→ Is there any problem on the WebLogic console in general? Sometimes, network issues can affect WebLogic console and WLSDM console… Please check ConnectionDelayTime on Datasources dashbaord and let us know any sudden increment for this MBean…