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.
NB 6.0 200704061800 & Glassfish v2 b50 + JDK 1.6 u1 on solaris sparc. Starting a local default domain in Profile Mode is done with success, but if we call Stop Action we get a ClassNotFoundException in the Output/Server.log but status of the instance in IDE is changed to stop. A Start in normal mode after this exception is ok. ... start Profiler Agent: Initializing... Profiler Agent: Options: >/opt/netbeans-6.0-040607/profiler2/lib,5140< Profiler Agent: Initialized succesfully Could not load Logmanager "com.sun.enterprise.server.logging.ServerLogManager" java.lang.ClassNotFoundException: com.sun.enterprise.server.logging.ServerLogManager at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.util.logging.LogManager$1.run(LogManager.java:166) at java.security.AccessController.doPrivileged(Native Method) at java.util.logging.LogManager.<clinit>(LogManager.java:156) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:169) at com.sun.jmx.trace.Trace.initDestination(Trace.java:46) at com.sun.jmx.trace.Trace.<clinit>(Trace.java:25) at javax.management.MBeanServerFactory.debug(MBeanServerFactory.java:524) at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:483) at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:511) at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:298) at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:213) at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:174) at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:302) at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504) at com.sun.tools.profiler.server.system.HeapDump.initialize16(HeapDump.java:50) at com.sun.tools.profiler.server.system.HeapDump.initialize(HeapDump.java:38) at com.sun.tools.profiler.server.ProfilerInterface.initProfilerInterface(ProfilerInterface.java:99) at com.sun.tools.profiler.server.ProfilerServer.initSupportingFunctionality(ProfilerServer.java:189) at com.sun.tools.profiler.server.ProfilerServer.doActivate(ProfilerServer.java:424) at com.sun.tools.profiler.server.ProfilerServer.activate(ProfilerServer.java:366) Failed to load MBeanServerBuilder class com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder: java.lang.ClassNotFoundException: com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
Opened GF issue to tat tracks a similar issue: https://glassfish.dev.java.net/issues/show_bug.cgi?id=3256 Same ST... different steps. If I use jdk 5 to start the server... I don't run into this exception, so it is likely to be a server/jdk interop issue...
*** Issue 108732 has been marked as a duplicate of this issue. ***
Comments or suggestions? Please provide info to the engineer working on the Glassfish issue: https://glassfish.dev.java.net/issues/show_bug.cgi?id=3256 This is a bug appears to be between the profiler and the app server and the jdk. The plgin doesn't do anything different if when JDK is used.
The exception is now harmless, since profiler has workaround for this problem. See issue #92236. The problem happens only on JKD6 since java.lang.management.ManagementFactory.getPlatformMBeanServer() is invoked by profiler only on JDK6.
An exception in the log is hardly ever harmless. Our goal should be to never produce a harmless message in the log, since these messages confuse users when they are trying to resolve real issues and make our products look buggy. If the ST is still generated, then this issue should probably be left open... at P3
Exception is there to see if the root problem is fixed in Glassfish. It will be disabled in FCS.
If there is a code change that you need to make in the profiler to prevent this exception from getting created in the server's log file... how can you consider this issue fixed?
*** Issue 135974 has been marked as a duplicate of this issue. ***