glassfish
  1. glassfish
  2. GLASSFISH-13779

WARNING's about update center after asupgrade from V2.1.1 to V3.1

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Incomplete
    • Affects Version/s: 3.1
    • Fix Version/s: not determined
    • Component/s: update_center
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: Macintosh

    • Issuezilla Id:
      13,779

      Description

      After starting the V3.1 domain after performing an asupgrade of a V2.1.1 domain
      to a V3.1 domain I notice these warning messages occurring regarding update
      center functionality in the server.log file.

      [#|2010-10-04T13:16:45.035-0400|WARNING|glassfish3.1|null|_ThreadID=17;_ThreadName=Thread-1;|!!!!!
      Cannot create Update Center Image for
      /sun/glassfishv2.1.1/glassfishv3/glassfish/..|#]
      .
      .
      .

      [#|2010-10-04T13:17:56.816-0400|WARNING|glassfish3.1|org.glassfish.admingui|_ThreadID=17;_ThreadName=Thread-1;|Cannot
      create update center Image for /sun/glassfishv2.1.1/glassfishv3; Update Center
      functionality will not be available in Admin Console |#]

      [#|2010-10-04T13:17:56.816-0400|WARNING|glassfish3.1|org.glassfish.admingui|_ThreadID=17;_ThreadName=Thread-1;|Error
      in getting update component list, cannot get image.|#]

      [#|2010-10-04T13:17:56.816-0400|INFO|glassfish3.1|org.glassfish.admingui|_ThreadID=17;_ThreadName=Thread-1;|Update
      Component count = -1|#]

        Activity

        Hide
        Snjezana Sevo-Zenzerovic added a comment -

        Could you please describe the exact procedure you used to install 3.1
        installation used in this scenario? Did you use IPS enabled image (either zip or
        installer bundle) coming from promoted RE build or something else?

        Show
        Snjezana Sevo-Zenzerovic added a comment - Could you please describe the exact procedure you used to install 3.1 installation used in this scenario? Did you use IPS enabled image (either zip or installer bundle) coming from promoted RE build or something else?
        Hide
        adf59 added a comment -

        The glassfish.zip was from my own svn child repository workspace that was build
        using the latest check'ins as of this morning. I basically just unzipped the
        glassfish.zip in the distributions directory after the mvn clean install was
        completed.

        Show
        adf59 added a comment - The glassfish.zip was from my own svn child repository workspace that was build using the latest check'ins as of this morning. I basically just unzipped the glassfish.zip in the distributions directory after the mvn clean install was completed.
        Hide
        Snjezana Sevo-Zenzerovic added a comment -

        Note that the distribution built in default developer profile is not IPS
        enabled and it is therefore expected that update check hook does not recognize
        this installation directory as valid IPS image. Functionality other than update
        client is not affected.

        I am closing the issue as "invalid" since this warning is expected in this
        particular scenario. If you use "official" IPS enabled distribution warning will
        go away.

        Show
        Snjezana Sevo-Zenzerovic added a comment - Note that the distribution built in default developer profile is not IPS enabled and it is therefore expected that update check hook does not recognize this installation directory as valid IPS image. Functionality other than update client is not affected. I am closing the issue as "invalid" since this warning is expected in this particular scenario. If you use "official" IPS enabled distribution warning will go away.

          People

          • Assignee:
            Snjezana Sevo-Zenzerovic
            Reporter:
            adf59
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: