java.lang.IllegalArgumentException: JNDI naming exception: null

Oracle Community | 3004 | 2 decades ago
  1. 0

    jndi exception using weblogic.Admin

    Oracle Community | 2 decades ago | 3004
    java.lang.IllegalArgumentException: JNDI naming exception: null
  2. 0

    IBM Health Monitor connects as anonymous to perform MBean lookup for JMS Queue Depth - United States

    ibm.com | 8 months ago
    java.lang.IllegalArgumentException: JNDI naming exception: javax.naming.NoPermissionException: User <anonymous> does not have permission on weblogic.management.adminhome to perform lookup operation. [Root exception is javax.naming.NoPermissionException: User <anonymous> does not have permission on weblogic.management.adminhome to perform lookup operation.]
  3. 0
    Some bots are sending malformed HTTP requests to your site. Try to find their IP addresses in the access logs and ask them to fix the bots or blacklist them.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0
    This error is caused by malformed HTTP request. You are trying to access unsecured page through https.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.IllegalArgumentException

      JNDI naming exception: null

      at weblogic.management.commandline.CommandLine.findMBeanHome()
    2. weblogic.management.commandline
      CommandLine.<init>
      1. weblogic.management.commandline.CommandLine.findMBeanHome(CommandLine.java:460)
      2. weblogic.management.commandline.CommandLine.doCommandline(CommandLine.java:86)
      3. weblogic.management.commandline.CommandLine.<init>(CommandLine.java:69)
      3 frames
    3. weblogic
      Admin.main
      1. weblogic.Admin.main(Admin.java:689)
      1 frame