Similar error occurs when starting a non-default local domain
e.g. create-domain --adminport 10000 domain2

register this domain in netbeans > start the domain

window pop-up prompt user and password, gives values for the above

receive the following error:

----Log File Rotated---
Apr 4, 2007 4:25:05 PM com.sun.enterprise.admin.servermgmt.launch.ASLauncher
buildCommand
INFO: 
/usr/java/jdk1.5.0_06/bin/java
-client
-XX:+UnlockDiagnosticVMOptions
-XX:MaxPermSize=192m
-Xmx512m
-XX:NewRatio=2
-XX:+LogVMOutput
-XX:LogFile=/opt/SUNWappserver91/domains/domain2/logs/jvm.log
-Dcom.sun.aas.ClassPathPrefix=
-Dcom.sun.aas.ClassPathSuffix=
-Dcom.sun.aas.ServerClassPath=
-Dcom.sun.aas.classloader.appserverChainJars.ee=
-Dcom.sun.aas.classloader.appserverChainJars=admin-cli.jar,admin-cli-ee.jar,dbschema.jar,j2ee-svc.jar
-Dcom.sun.aas.classloader.optionalOverrideableChain.ee=
-Dcom.sun.aas.classloader.optionalOverrideableChain=webservices-rt.jar,webservices-tools.jar,commons-logging.jar,commons-launcher.jar
-Dcom.sun.aas.classloader.serverClassPath.ee=Does not
exist/lib/hadbjdbc4.jar,/opt/SUNWappserver91/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,Does
not exist/lib/dbstate.jar,Does not exist/lib/hadbm.jar,Does not
exist/lib/hadbmgt.jar,/opt/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Dcom.sun.aas.classloader.serverClassPath=/opt/SUNWappserver91/lib/install/applications/jmsra/imqjmsra.jar,/opt/SUNWappserver91/imq/lib/jaxm-api.jar,/opt/SUNWappserver91/imq/lib/fscontext.jar,/opt/SUNWappserver91/imq/lib/imqbroker.jar,/opt/SUNWappserver91/imq/lib/imqjmx.jar,/opt/SUNWappserver91/lib/ant/lib/ant.jar,/opt/SUNWappserver91/lib/SUNWjdmk/5.1/lib/jdmkrt.jar
-Dcom.sun.aas.classloader.sharedChainJars.ee=appserv-se.jar,appserv-ee.jar,Does
not exist/lib/dbstate.jar,Does not
exist/lib/hadbjdbc4.jar,jgroups-all.jar,/opt/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Dcom.sun.aas.classloader.sharedChainJars=javaee.jar,/usr/java/jdk1.5.0_06/lib/tools.jar,install/applications/jmsra/imqjmsra.jar,commons-launcher.jar,/opt/SUNWappserver91/imq/lib/jaxm-api.jar,/opt/SUNWappserver91/imq/lib/fscontext.jar,/opt/SUNWappserver91/imq/lib/imqbroker.jar,/opt/SUNWappserver91/imq/lib/imqjmx.jar,/opt/SUNWappserver91/imq/lib/imqxm.jar,/opt/SUNWappserver91/lib/ant/lib/ant.jar,webservices-rt.jar,webservices-tools.jar,mail.jar,jsf-api.jar,jsf-impl.jar,appserv-jstl.jar,appserv-env.jar,jmxremote_optional.jar,/opt/SUNWappserver91/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,commons-logging.jar,activation.jar,appserv-rt.jar,appserv-admin.jar,appserv-cmp.jar,/opt/SUNWappserver91/updatecenter/lib/updatecenter.jar,/opt/SUNWappserver91/jbi/lib/jbi.jar
-Dcom.sun.aas.configName=server-config
-Dcom.sun.aas.configRoot=/opt/SUNWappserver91/config
-Dcom.sun.aas.defaultLogFile=/opt/SUNWappserver91/domains/domain2/logs/server.log
-Dcom.sun.aas.domainName=domain2
-Dcom.sun.aas.installRoot=/opt/SUNWappserver91
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.instanceRoot=/opt/SUNWappserver91/domains/domain2
-Dcom.sun.aas.processLauncher=SE
-Dcom.sun.aas.promptForIdentity=true
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.help,javax.portlet
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Dcom.sun.updatecenter.home=/opt/SUNWappserver91/updatecenter
-Ddomain.name=domain2
-Djava.endorsed.dirs=/opt/SUNWappserver91/lib/endorsed
-Djava.ext.dirs=/usr/java/jdk1.5.0_06/lib/ext:/usr/java/jdk1.5.0_06/jre/lib/ext:/opt/SUNWappserver91/domains/domain2/lib/ext:/opt/SUNWappserver91/javadb/lib
-Djava.library.path=/opt/SUNWappserver91/lib:/opt/SUNWappserver91/lib:/opt/SUNWappserver91/lib
-Djava.security.auth.login.config=/opt/SUNWappserver91/domains/domain2/config/login.conf
-Djava.security.policy=/opt/SUNWappserver91/domains/domain2/config/server.policy
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Djavax.net.ssl.keyStore=/opt/SUNWappserver91/domains/domain2/config/keystore.jks
-Djavax.net.ssl.trustStore=/opt/SUNWappserver91/domains/domain2/config/cacerts.jks
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Djmx.invoke.getters=true
-Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000
-cp
:/opt/SUNWappserver91/lib/appserv-launch.jar
com.sun.enterprise.server.PELaunch
start
Apr 4, 2007 4:25:05 PM com.sun.enterprise.admin.servermgmt.launch.ASLauncher process
INFO: goodbye
Starting Sun Java System Application Server 9.1 (build b41-beta2) ...
CORE5098: AS Socket Service Initialization has been completed.
CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.5.0_06] from [Sun
Microsystems Inc.]
SEC1002: Security Manager is OFF.
ADM0001:MBeanServer initialized successfully
SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.
WEB0114: SSO is disabled in virtual server [server]
WEB0114: SSO is disabled in virtual server [__asadmin]
RMIClient.getRMIClient: server
ADM1079: Initialization of AMX MBeans successful
ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer:
[service:jmx:rmi:///jndi/rmi://easqelx10:60604/jmxrmi].  This is where the
remote administrative clients should connect using the standard JMX connectors
ADM1506: Status of Standard JMX Connector: Active = [true]
[AutoDeploy] Selecting file
/opt/SUNWappserver91/lib/install/applications/__ejb_container_timer_app.ear for
autodeployment.
deployed with moduleid = __ejb_container_timer_app
[AutoDeploy] Successfully autodeployed :
/opt/SUNWappserver91/lib/install/applications/__ejb_container_timer_app.ear.
[AutoDeploy] Selecting file
/opt/SUNWappserver91/lib/install/applications/__JWSappclients.ear for
autodeployment.
deployed with moduleid = __JWSappclients
[AutoDeploy] Successfully autodeployed :
/opt/SUNWappserver91/lib/install/applications/__JWSappclients.ear.
[AutoDeploy] Selecting file
/opt/SUNWappserver91/lib/install/applications/MEjbApp.ear for autodeployment.
deployed with moduleid = MEjbApp
[AutoDeploy] Successfully autodeployed :
/opt/SUNWappserver91/lib/install/applications/MEjbApp.ear.
WEB0302: Starting Sun-Java-System/Application-Server.
JBIFW0010: JBI framework ready to accept requests.
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 60598
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 60601
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 10000
SMGT0007: Self Management Rules service is enabled
Application server startup complete.
Initializing Sun's JavaServer Faces implementation (1.2_04-b10-p01) for context ''
RMIClient.getRMIClient: server
SEC5046: Audit: Authentication refused for [].
Web login failed: Login failed: javax.security.auth.login.LoginException: Failed
file login for .
RMIClient.getRMIClient: server
SEC5046: Audit: Authentication refused for [].
Web login failed: Login failed: javax.security.auth.login.LoginException: Failed
file login for .
SEC5046: Audit: Authentication refused for [admin].
Web login failed: Login failed: javax.security.auth.login.LoginException: Failed
file login for admin.
SEC5046: Audit: Authentication refused for [admin].
Web login failed: Login failed: javax.security.auth.login.LoginException: Failed
file login for admin.
SEC5046: Audit: Authentication refused for [admin].
Web login failed: Login failed: javax.security.auth.login.LoginException: Failed
file login for admin.
SEC5046: Audit: Authentication refused for [admin].
Web login failed: Login failed: javax.security.auth.login.LoginException: Failed
file login for admin.

Start can be done without a password. But populating the runtime tab involves
calls which require authentication by the server. This is 'normal' error reporting
in the app server log.
Not nice, but I don't think much can be done about this.

Maybe a passthrough of runtime tree creation code to minimize number of invokes
on server. But I think that this exercise was already done 

Lowering to P3 and revisit

this doesn't seem to be an issue anymore.  i just tried it and I only see one of the auth refused messages per action on
the domains node...

may have been addressed by changes that I made to eliminate the looping authentication issues, too....