glassfish
  1. glassfish
  2. GLASSFISH-14963

upgrading from v2.1 domain.xml does not add a default-config entry

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 3.1_ms07
    • Component/s: configuration, upgrade_tool
    • Labels:
      None

      Description

      The resulting domain.xml only has the one config (name="server-config") after upgrading.

        Issue Links

          Activity

          Hide
          Tom Mueller added a comment -

          How did you get a v2.1 domain.xml that doesn't have a default-config defined in it?

          A domain by default has a default-config in it for 2.1.
          Please provide more details on the test case. What commands were executed in v2.1 before performing the upgrade?

          Show
          Tom Mueller added a comment - How did you get a v2.1 domain.xml that doesn't have a default-config defined in it? A domain by default has a default-config in it for 2.1. Please provide more details on the test case. What commands were executed in v2.1 before performing the upgrade?
          Hide
          Justin Lee added a comment -

          I installed v2 and copied out the domain.xml file it created. Otherwise, I haven't touched the file.

          Show
          Justin Lee added a comment - I installed v2 and copied out the domain.xml file it created. Otherwise, I haven't touched the file.
          Hide
          Nazrul added a comment -

          v2 developer profile does not have default-config in domain.xml.

          Show
          Nazrul added a comment - v2 developer profile does not have default-config in domain.xml.
          Hide
          Tom Mueller added a comment -

          A 2.1 developer profile system doesn't have a default-config, so when this is upgraded to 3.1, it is expected to not have a default-config either. If the user wants to use clustering features in 3.1 based on an upgraded 2.1 developer domain, they have several options:

          1. Use the 2.1 feature to upgrade the domain to the enterprise profile before upgrading to 3.1.
          2. Create a default-config in 3.1 using asadmin copy-config command.

          Creating a default-config automatically as part of an upgrade would involve an assumption that the user actually wants that created as part of the upgrade.

          Show
          Tom Mueller added a comment - A 2.1 developer profile system doesn't have a default-config, so when this is upgraded to 3.1, it is expected to not have a default-config either. If the user wants to use clustering features in 3.1 based on an upgraded 2.1 developer domain, they have several options: 1. Use the 2.1 feature to upgrade the domain to the enterprise profile before upgrading to 3.1. 2. Create a default-config in 3.1 using asadmin copy-config command. Creating a default-config automatically as part of an upgrade would involve an assumption that the user actually wants that created as part of the upgrade.

            People

            • Assignee:
              Tom Mueller
              Reporter:
              Justin Lee
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: