glassfish
  1. glassfish
  2. GLASSFISH-4551

ManagementFactory.getPlatformMBeanServer causes ClassNotFoundException

    Details

    • Issuezilla Id:
      4,551
    • Status Whiteboard:
      Hide

      as911-na

      Show
      as911-na

      Description

      We at the NetBeans Profiler team are still experiencing problems as described in
      the issue https://glassfish.dev.java.net/issues/show_bug.cgi?id=1409.
      The only difference is that the problems manifests itself only if using
      clustered environment. For single instance setup it works correctly.
      Also, there is a P2 issue filed for Profiler which is a direct result of the
      aforementioned problem.
      Will attach domain.xml and log file.

      1. domain.xml
        39 kB
        yardus
      2. server.log
        194 kB
        yardus

        Activity

        Hide
        yardus added a comment -

        Created an attachment (id=1416)
        domain.xml

        Show
        yardus added a comment - Created an attachment (id=1416) domain.xml
        Hide
        yardus added a comment -

        Created an attachment (id=1417)
        server.log

        Show
        yardus added a comment - Created an attachment (id=1417) server.log
        Hide
        yardus added a comment -
        Show
        yardus added a comment - The dependent profiler issue: http://www.netbeans.org/issues/show_bug.cgi?id=117464
        Hide
        dochez added a comment -

        9.1 mbeanserver issue

        Show
        dochez added a comment - 9.1 mbeanserver issue
        Hide
        harpreet added a comment -

        Marking target milestone as 9.1.1

        Show
        harpreet added a comment - Marking target milestone as 9.1.1
        Hide
        km added a comment -

        yardus, can you tell us the severity of this problem? I think the problem is in
        setting up the correct classpath in EE case, so that the server finds the
        necessary classes.

        harpreet – depending upon submitter's response, we may want to fix it. But
        since this is rather old, I am not sure if enough people will run into it.

        Byron – please take a look.

        Show
        km added a comment - yardus, can you tell us the severity of this problem? I think the problem is in setting up the correct classpath in EE case, so that the server finds the necessary classes. harpreet – depending upon submitter's response, we may want to fix it. But since this is rather old, I am not sure if enough people will run into it. Byron – please take a look.
        Hide
        yardus added a comment -

        As for severity - it practically prevents profiling of glassfish instances
        participating in a cluster. Failing to resolve this issue will make the bad
        impression of not being able to use Sun tools to profile Sun application server

        Show
        yardus added a comment - As for severity - it practically prevents profiling of glassfish instances participating in a cluster. Failing to resolve this issue will make the bad impression of not being able to use Sun tools to profile Sun application server
        Hide
        harpreet added a comment -

        Please scrub issue and see if it is critical to v2.1.

        Show
        harpreet added a comment - Please scrub issue and see if it is critical to v2.1.
        Hide
        Nazrul added a comment -

        Requesting Sreeni to evaluate this issue.

        Show
        Nazrul added a comment - Requesting Sreeni to evaluate this issue.
        Hide
        msreddy added a comment -

        I am able to reproduce the reported issue on windows as given below.

        01 Built AS 9.1.1 on windows.
        02 Installed Netbeans IDE 6.1 with web distribution.
        03 Started netbeans, added server on Services tab
        04 Started server in profile mode and attached the profiler, it worked fine only
        for the first time.
        05 Created a second domain, started in profile mode, attached profiler. Ran for
        10 seconds and hung with the excption given below.
        Because of freeze, I had to restart the machine.
        After restarting, when I start either domain (default or newly created) it is
        not able to start in profiler mode and similar log message is displayed.

        At this time, I think it is caused during the launch process (it may not have
        gotten to the log manager yet) and I don't see any additional info to debug this
        further.

        Since submitter feels that it is critical, suggest that some one faimilar with
        launcher looks at this.

        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:307)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
        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
        org.netbeans.lib.profiler.server.system.HeapDump.initialize16(HeapDump.java:102)
        at
        org.netbeans.lib.profiler.server.system.HeapDump.initialize(HeapDump.java:78)
        at
        org.netbeans.lib.profiler.server.ProfilerInterface.initProfilerInterface(ProfilerInterface.java:464)
        at
        org.netbeans.lib.profiler.server.ProfilerServer.initSupportingFunctionality(ProfilerServer.java:973)
        at
        org.netbeans.lib.profiler.server.ProfilerServer.doActivate(ProfilerServer.java:904)
        at
        org.netbeans.lib.profiler.server.ProfilerServer.activate(ProfilerServer.java:512)
        Failed to load MBeanServerBuilder class
        com.sun.enterprise.ee.admin.AppServerMBeanServerBuilder:
        java.lang.ClassNotFoundException:
        com.sun.enterprise.ee.admin.AppServerMBeanServerBuilder
        Profiler Agent: Initializing...
        Profiler Agent: Options: >"C:\Program Files\NetBeans 6.1\profiler3\lib",5140<

        Show
        msreddy added a comment - I am able to reproduce the reported issue on windows as given below. 01 Built AS 9.1.1 on windows. 02 Installed Netbeans IDE 6.1 with web distribution. 03 Started netbeans, added server on Services tab 04 Started server in profile mode and attached the profiler, it worked fine only for the first time. 05 Created a second domain, started in profile mode, attached profiler. Ran for 10 seconds and hung with the excption given below. Because of freeze, I had to restart the machine. After restarting, when I start either domain (default or newly created) it is not able to start in profiler mode and similar log message is displayed. At this time, I think it is caused during the launch process (it may not have gotten to the log manager yet) and I don't see any additional info to debug this further. Since submitter feels that it is critical, suggest that some one faimilar with launcher looks at this. 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:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) 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 org.netbeans.lib.profiler.server.system.HeapDump.initialize16(HeapDump.java:102) at org.netbeans.lib.profiler.server.system.HeapDump.initialize(HeapDump.java:78) at org.netbeans.lib.profiler.server.ProfilerInterface.initProfilerInterface(ProfilerInterface.java:464) at org.netbeans.lib.profiler.server.ProfilerServer.initSupportingFunctionality(ProfilerServer.java:973) at org.netbeans.lib.profiler.server.ProfilerServer.doActivate(ProfilerServer.java:904) at org.netbeans.lib.profiler.server.ProfilerServer.activate(ProfilerServer.java:512) Failed to load MBeanServerBuilder class com.sun.enterprise.ee.admin.AppServerMBeanServerBuilder: java.lang.ClassNotFoundException: com.sun.enterprise.ee.admin.AppServerMBeanServerBuilder Profiler Agent: Initializing... Profiler Agent: Options: >"C:\Program Files\NetBeans 6.1\profiler3\lib",5140<
        Hide
        msreddy added a comment -

        Reassiging to Byron for his help with the launcher code.

        Show
        msreddy added a comment - Reassiging to Byron for his help with the launcher code.
        Hide
        msreddy added a comment -

        Based on discussion with Yardus (the submitter) it is important that we get this
        fixed for latest v3 version. Once we make sure that it works for v3, and since
        it works with domain, the priority may be reduced for v2.

        We need to work closely with Yardus to understand the profiler interaction with
        launcher to fix this issue.

        Show
        msreddy added a comment - Based on discussion with Yardus (the submitter) it is important that we get this fixed for latest v3 version. Once we make sure that it works for v3, and since it works with domain, the priority may be reduced for v2. We need to work closely with Yardus to understand the profiler interaction with launcher to fix this issue.
        Hide
        Nazrul added a comment -

        ...

        Show
        Nazrul added a comment - ...
        Hide
        harpreet added a comment -

        Based on Sreeni's comments it looks like the issue is not critical to v2.1. Removing it from the approved
        list. Sreeni can you comment on the underlying cause.

        Show
        harpreet added a comment - Based on Sreeni's comments it looks like the issue is not critical to v2.1. Removing it from the approved list. Sreeni can you comment on the underlying cause.
        Hide
        msreddy added a comment -

        pl. see my comment on 03nov08

        Show
        msreddy added a comment - pl. see my comment on 03nov08
        Hide
        sanandal added a comment -

        "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
        release whose primary release driver is SailFin.
        This issue will be scrubbed after this release and will be given the right
        priority for the next release."

        Show
        sanandal added a comment - "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1 release whose primary release driver is SailFin. This issue will be scrubbed after this release and will be given the right priority for the next release."
        Hide
        jchristi added a comment -

        adding me to cc

        Show
        jchristi added a comment - adding me to cc
        Hide
        hegalor added a comment -

        Would be nice, if that issue could be fixed.

        Show
        hegalor added a comment - Would be nice, if that issue could be fixed.
        Hide
        Tom Mueller added a comment -

        Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

        Show
        Tom Mueller added a comment - Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

          People

          • Assignee:
            msreddy
            Reporter:
            yardus
          • Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: