Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.1
    • Fix Version/s: 4.0
    • Component/s: admin
    • Labels:
      None

      Description

      Add one line of code to a core/kernel command.
      build
      copy the jar to modules
      (like I've done a million times before)

      Mar 9, 2011 5:56:39 PM Main start
      WARNING: Exception while starting bundle org.glassfish.core.kernel [71]
      org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.core.kernel [71]: Unable to resolve 71.0: missing requirement [71.0] package;
      (package=com.sun.management)
      at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3443)
      at org.apache.felix.framework.Felix.startBundle(Felix.java:1727)
      at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922)
      at org.jvnet.hk2.osgimain.Main.start(Main.java:157)
      at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
      at org.apache.felix.framework.Felix.activateBundle(Felix.java:1835)
      at org.apache.felix.framework.Felix.startBundle(Felix.java:1752)
      at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1156)
      at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
      at java.lang.Thread.run(Thread.java:662)

      ================

      The problem is that the server is in a Zombie state. It is not dead. It is not alive.
      Isn't this above problem catastrophic enough to warrant killing off the process?

      D:\gf\v3\core\kernel>jps
      6500 admin-cli.jar
      3880
      716 ASMain
      6412 Jps

        Activity

        Hide
        Tom Mueller added a comment -

        Is this a problem in the bootstrap area or AppServerStartup in that it is not detecting the failure to actually start the system?

        Byron, can you please provide an example of the type of change that results in this problem?

        Show
        Tom Mueller added a comment - Is this a problem in the bootstrap area or AppServerStartup in that it is not detecting the failure to actually start the system? Byron, can you please provide an example of the type of change that results in this problem?
        Hide
        Byron Nevins added a comment -

        No, sorry, I can't provide a reproducible way. It probably had something to do with switching back and forth between JDK6 and 7.

        All I did was add one or two lines of code to UptimeCommand (because it's a handy place to quickly add temporary runtime testing code). Once I got into his problem – it would not go away no matter what. Deleting the cache had zero affect. I had to reinstall GlassFish. The code I added was simply getting the OS MBean from the runtime mbean server.

        It should be straight-forward to coax a failure like I had for a savvy OSGi developer/user – I would imagine. That would not be me.

        Show
        Byron Nevins added a comment - No, sorry, I can't provide a reproducible way. It probably had something to do with switching back and forth between JDK6 and 7. All I did was add one or two lines of code to UptimeCommand (because it's a handy place to quickly add temporary runtime testing code). Once I got into his problem – it would not go away no matter what. Deleting the cache had zero affect. I had to reinstall GlassFish. The code I added was simply getting the OS MBean from the runtime mbean server. It should be straight-forward to coax a failure like I had for a savvy OSGi developer/user – I would imagine. That would not be me.
        Hide
        Sanjeeb Sahoo added a comment -

        We should use a finite timeout in waitForService call so that the process dies...

        Show
        Sanjeeb Sahoo added a comment - We should use a finite timeout in waitForService call so that the process dies...
        Hide
        Sanjeeb Sahoo added a comment -

        Happens in dev env, so reducing the priority

        Show
        Sanjeeb Sahoo added a comment - Happens in dev env, so reducing the priority

          People

          • Assignee:
            Sanjeeb Sahoo
            Reporter:
            Byron Nevins
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: