java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console

JBoss Issue Tracker | Len DiMaggio | 9 years ago
  1. 0

    Description of problem: jboss_init_redhat.sh - fails to shutdown service - Failed to authenticate principal=null, securityDomain=jmx-console Version-Release number of selected component (IR or RC #, component ver) soa-4.2.0-IR8.0.zip How reproducible: 100% Steps to Reproduce: 1. Copy jboss_init_redhat.sh to /etc/init.d/jboss and run /sbin/service jboss start - or from in jboss-soa-p.4.2.0/jboss-as/bin run sh ./jboss_init_redhat.sh start 2. Try sbin/service jboss stop - or from in jboss-soa-p.4.2.0/jboss-as/bin run sh ./jboss_init_redhat.sh stop Actual results: These errors are written to the server log: 2007-12-11 14:42:33,623 DEBUG [org.jboss.security.auth.spi.UsersRolesLoginModule] Loaded properties, users=[admin] 2007-12-11 14:42:33,624 DEBUG [org.jboss.security.auth.spi.UsersRolesLoginModule] Loaded properties, users=[admin] 2007-12-11 14:42:33,624 DEBUG [org.jboss.security.auth.spi.UsersRolesLoginModule] Bad password for username=null And the server is not stopped. If you run the command from the CLI - this exception is displayed: + su - jboss -c 'java -classpath /opt/IR8/jboss-soa-p.4.2.0/jboss-as/bin/shutdown.jar:/opt/IR8/jboss-soa-p.4.2.0/jboss-as/client/jnet.jar org.jboss.Shutdown --shutdown' Password: Exception in thread "main" java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) 2007-12-11 14:42:33,623 DEBUG [org.jboss.security.auth.spi.UsersRolesLoginModule] Loaded properties, users=[admin, root, jboss] 2007-12-11 14:42:33,624 DEBUG [org.jboss.security.auth.spi.UsersRolesLoginModule] Loaded properties, users=[admin] 2007-12-11 14:42:33,624 DEBUG [org.jboss.security.auth.spi.UsersRolesLoginModule] Bad password for username=null Expected results: The server should be stopped. Additional info: I tried adding both root and the user used to start the jboss server to jboss-soa-p.4.2.0/jboss-as/server/production/conf/props/soa-users.properties - but this didn't help. What user definition is needed here?

    JBoss Issue Tracker | 9 years ago | Len DiMaggio
    java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
  2. 0

    Authentication in Remote Connection to JBoss 4.2.3

    Stack Overflow | 4 years ago | cneller
    java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
  3. 0

    Thoughts From A Management Platform Developer: Transaction Recovery in JBossAS

    blogspot.com | 2 years ago
    java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    db:: 3.65::exception on JBoss startup 38

    hivmr.com | 11 months ago
    java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console

    1 unregistered visitors
    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.SecurityException

      Failed to authenticate principal=null, securityDomain=jmx-console

      at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke()
    2. JBoss Application Server Server
      AuthenticationInterceptor.invoke
      1. org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97)
      1 frame
    3. JBoss Application Server J2SE
      Invocation.invoke
      1. org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
      1 frame