java.lang.IllegalArgumentException: ObjectName must not be null

Oracle Community | a73210 | 6 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.

Root Cause Analysis

  1. java.lang.IllegalArgumentException

    ObjectName must not be null

    at javax.management.remote.rmi.RMIConnectionImpl.checkNonNull()
  2. Java RT
    RMIConnectionImpl_WLSkel.invoke
    1. javax.management.remote.rmi.RMIConnectionImpl.checkNonNull(RMIConnectionImpl.java:1623)
    2. javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:761)
    3. javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
    3 frames
  3. weblogic.rmi.internal
    BasicServerRef$1.run
    1. weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
    2. weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
    2 frames
  4. weblogic.security.acl
    AuthenticatedSubject.doAs
    1. weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    1 frame
  5. weblogic.security.service
    SecurityManager.runAs
    1. weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    1 frame
  6. weblogic.rmi.internal
    WLSExecuteRequest.run
    1. weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
    2. weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    2 frames
  7. weblogic.work
    ExecuteThread.run
    1. weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    2. weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    2 frames