This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 211879 - SecurityException: Failed to authenticate principal=admin, securityDomain=jmx-console
Summary: SecurityException: Failed to authenticate principal=admin, securityDomain=jmx...
Status: RESOLVED INCOMPLETE
Alias: None
Product: serverplugins
Classification: Unclassified
Component: JBoss (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-30 19:57 UTC by kartik.boreda
Modified: 2015-07-15 11:44 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 187521


Attachments
stacktrace (3.68 KB, text/plain)
2012-04-30 19:57 UTC, kartik.boreda
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kartik.boreda 2012-04-30 19:57:03 UTC
This bug was originally marked as duplicate of bug 161276, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 7.1.1 (Build 201203012225)
VM: Java HotSpot(TM) 64-Bit Server VM, 20.6-b01, Java(TM) SE Runtime Environment, 1.6.0_31-b05
OS: Windows 7

Stacktrace: 
java.lang.SecurityException: Failed to authenticate principal=admin, securityDomain=jmx-console
   at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
   at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:0)
Comment 1 kartik.boreda 2012-04-30 19:57:10 UTC
Created attachment 118900 [details]
stacktrace
Comment 2 Petr Hejl 2015-07-15 11:44:47 UTC
Is there any way to reproduce this? It looks like this happened to 1 user in 1 build...