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.
Summary: | Cannot profile j2ee application using glassfish | ||
---|---|---|---|
Product: | profiler | Reporter: | ehucka <ehucka> |
Component: | Base | Assignee: | Tomas Hurka <thurka> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | ||
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 91682 | ||
Attachments: | crash log |
Description
ehucka
2007-01-10 16:00:17 UTC
Eman, should this issue be considered as a show stopper for M6? Set as showstopper for m6. Local direct attach to a glassfish produced this exception: 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:268) 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:164) 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:543) at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServ erFactory.java:502) at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanSer verFactory.java:530) at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory .java:304) at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFact ory.java:219) at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFact ory.java:180) at sun.management.ManagementFactory.createPlatformMBeanServer(Management Factory.java:264) at java.lang.management.ManagementFactory.getPlatformMBeanServer(Managem entFactory.java:512) at com.sun.tools.profiler.server.system.HeapDump.initialize(HeapDump.jav a:33) at com.sun.tools.profiler.server.ProfilerInterface.initProfilerInterface (ProfilerInterface.java:98) at com.sun.tools.profiler.server.ProfilerServer.initSupportingFunctional ity(ProfilerServer.java:186) at com.sun.tools.profiler.server.ProfilerServer.doActivate(ProfilerServe r.java:394) at com.sun.tools.profiler.server.ProfilerServer.activate(ProfilerServer. java:345) # # An unexpected error has been detected by HotSpot Virtual Machine: # # Internal Error (455843455054494F4E530E4350500112), pid=5384, tid=4764 # # Java VM: Java HotSpot(TM) Client VM (1.5.0_11-b03 mixed mode) # An error report file with more information is saved as hs_err_pid5384.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Profiler Agent: Initializing... Profiler Agent: Options: >"E:\Builds\dev\NetBeans m6\profiler1\lib",5140< Profiler Agent: Initialized succesfully Is it related to this issue? Emane yes, it is. It is a bug in glassfish and/or JDK. Please attach crash log. See https://glassfish.dev.java.net/issues/show_bug.cgi?id=1409 Please add your comments to glassfish issue and also report JDK crash. I will try to find some workaround. Created attachment 37251 [details]
crash log
Please add bug ID and link to JDK bug. Workaround found and committed to trunk. It was reported as jdk bug 6512128. verified |