glassfish
  1. glassfish
  2. GLASSFISH-15544

[BLOCKING] Cannot login to GUI after upgraded from v2 applying Glassfish 2.1.1Patch8 Enterprise profile

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 3.1_b35
    • Fix Version/s: 3.1_b39
    • Component/s: admin_gui
    • Labels:
      None
    • Environment:

      Solaris sparc

      Description

      Glassfish 2.1.1 Patch8 to 3.1 B35 Upgrade in Enterprise profile.

      Follow the steps as per http://java.net/jira/browse/GLASSFISH-15108

      After upgrade try to load the admin console at 4848, it does not load and throws a
      " Authentication failed " message. Please see the attachment upgraded-admin-b35-jdk6u23.png

      1. domain_after_upgrade.xml
        49 kB
        Bobby Bissett
      2. domain_before_upgrade.xml
        58 kB
        Bobby Bissett
      3. server.b38.log
        136 kB
        sss150302
      4. server.log
        184 kB
        sss150302
      5. server-cannotCreatClassLoader.log
        34 kB
        Anissa Lam
      6. upgrade-31-b38.log
        16 kB
        sss150302
      7. upgrade-31-b39-nightly-20-jan-2011.log
        23 kB
        sss150302
      1. adminconsole-auth-module.jpg
        216 kB
      2. console-screen-b38.jpg
        111 kB
      3. upgraded-admin-b35-jdk6u23.png
        73 kB

        Issue Links

          Activity

          Hide
          Bobby Bissett added a comment -

          This is already a known issue. See GLASSFISH-15441 and GLASSFISH-15519.

          Show
          Bobby Bissett added a comment - This is already a known issue. See GLASSFISH-15441 and GLASSFISH-15519 .
          Hide
          Anissa Lam added a comment -

          Thanks for verifying. Please file a separate bug regarding the Bundle Exception. thanks.

          Show
          Anissa Lam added a comment - Thanks for verifying. Please file a separate bug regarding the Bundle Exception. thanks.
          Hide
          sss150302 added a comment - - edited

          Wow, Finally, the fix is working fine. Kudos to the teamwork!
          I have verified it with Latest Nightly Build B39, Dated 20 jan 2011.

          However I would not like to see the annoying Bundle exception in felix on the console as ( details log attached)as upgrade-31-b39-nightly-20-jan-2011.log

          Error while starting bundle: file:/space/31/upgrade/glassfish3/glassfish/modules/autostart/org.apache.felix.eventadmin.jar: org.osgi.framework.BundleException: Cannot start bundle org.apache.felix.eventadmin [245] because its start level is 1, which is greater than the framework's start level of 0.
          org.osgi.framework.BundleException: Cannot start bundle org.apache.felix.eventadmin [245] because its start level is 1, which is greater than the framework's start level of 0.
          at org.apache.felix.framework.Felix.startBundle(Felix.java:1690)
          at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922)
          at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1157)
          at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1135)
          at org.apache.felix.fileinstall.internal.DirectoryWatcher.processAllBundles(DirectoryWatcher.java:1128)
          at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:438)
          at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:245)
          Error while starting bundle: file:/space/31/upgrade/glassfish3/glassfish/modules/autostart/osgi-javaee-base.jar: org.osgi.framework.BundleException: Cannot start bundle org.glassfish.osgi-javaee-base [246] because its start level is 1, which is greater than the framework's start level of 0.
          org.osgi.framework.BundleException: Cannot start bundle org.glassfish.osgi-javaee-base [246] because its start level is 1, which is greater than the framework's start level of 0.
          at org.apache.felix.framework.Felix.startBundle(Felix.java:1690)
          at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922)
          at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1157)
          at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1135)
          at org.apache.felix.fileinstall.internal.DirectoryWatcher.processAllBundles(DirectoryWatcher.java:1128)
          at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:438)
          at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:245)
          Error while starting bundle: file:/space/31/upgrade/glassfish3/glassfish/modules/autostart/osgi-cdi.jar: org.osgi.framework.BundleException: Cannot start bundle org.glassfish.osgi-cdi [247] because its start level is 1, which is greater than the framework's start level of 0.
          org.osgi.framework.BundleException: Cannot start bundle org.glassfish.osgi-cdi [247] because its start level is 1, which is greater than the framework's start level of 0.
          at org.apache.felix.framework.Felix.startBundle(Felix.java:1690)
          at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922)
          at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1157)
          at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1135)
          at org.apache.felix.fileinstall.internal.DirectoryWatcher.processAllBundles(DirectoryWatcher.java:1128)
          at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:438)
          at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:245)

          Show
          sss150302 added a comment - - edited Wow, Finally, the fix is working fine. Kudos to the teamwork! I have verified it with Latest Nightly Build B39, Dated 20 jan 2011. However I would not like to see the annoying Bundle exception in felix on the console as ( details log attached)as upgrade-31-b39-nightly-20-jan-2011.log Error while starting bundle: file:/space/31/upgrade/glassfish3/glassfish/modules/autostart/org.apache.felix.eventadmin.jar: org.osgi.framework.BundleException: Cannot start bundle org.apache.felix.eventadmin [245] because its start level is 1, which is greater than the framework's start level of 0. org.osgi.framework.BundleException: Cannot start bundle org.apache.felix.eventadmin [245] because its start level is 1, which is greater than the framework's start level of 0. at org.apache.felix.framework.Felix.startBundle(Felix.java:1690) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922) at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1157) at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1135) at org.apache.felix.fileinstall.internal.DirectoryWatcher.processAllBundles(DirectoryWatcher.java:1128) at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:438) at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:245) Error while starting bundle: file:/space/31/upgrade/glassfish3/glassfish/modules/autostart/osgi-javaee-base.jar: org.osgi.framework.BundleException: Cannot start bundle org.glassfish.osgi-javaee-base [246] because its start level is 1, which is greater than the framework's start level of 0. org.osgi.framework.BundleException: Cannot start bundle org.glassfish.osgi-javaee-base [246] because its start level is 1, which is greater than the framework's start level of 0. at org.apache.felix.framework.Felix.startBundle(Felix.java:1690) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922) at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1157) at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1135) at org.apache.felix.fileinstall.internal.DirectoryWatcher.processAllBundles(DirectoryWatcher.java:1128) at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:438) at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:245) Error while starting bundle: file:/space/31/upgrade/glassfish3/glassfish/modules/autostart/osgi-cdi.jar: org.osgi.framework.BundleException: Cannot start bundle org.glassfish.osgi-cdi [247] because its start level is 1, which is greater than the framework's start level of 0. org.osgi.framework.BundleException: Cannot start bundle org.glassfish.osgi-cdi [247] because its start level is 1, which is greater than the framework's start level of 0. at org.apache.felix.framework.Felix.startBundle(Felix.java:1690) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922) at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1157) at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1135) at org.apache.felix.fileinstall.internal.DirectoryWatcher.processAllBundles(DirectoryWatcher.java:1128) at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:438) at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:245)
          Hide
          Anissa Lam added a comment -

          The fix didn't make it to build 38.

          According to this page: http://wikis.sun.com/display/GlassFish/3.1BuildSchedule
          Build 38 is based on rev# 44543
          and as specified in my comment, the rev with my fix is #44585

          Project: glassfish
          Repository: svn
          Revision: 44585
          Author: anilam
          Date: 2011-01-19 05:36:30 UTC
          Link:

          So, Sanjay, can you try to verify the fix using latest nightly build ? or build after 1/19 ?
          thanks

          Show
          Anissa Lam added a comment - The fix didn't make it to build 38. According to this page: http://wikis.sun.com/display/GlassFish/3.1BuildSchedule Build 38 is based on rev# 44543 and as specified in my comment, the rev with my fix is #44585 Project: glassfish Repository: svn Revision: 44585 Author: anilam Date: 2011-01-19 05:36:30 UTC Link: So, Sanjay, can you try to verify the fix using latest nightly build ? or build after 1/19 ? thanks
          Hide
          Bobby Bissett added a comment -

          No, and I don't know when b38 was built.

          Show
          Bobby Bissett added a comment - No, and I don't know when b38 was built.

            People

            • Assignee:
              Anissa Lam
              Reporter:
              sss150302
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved: