Uploaded image for project: 'Codehaus Cargo'
  1. CARGO-1357

WebLogic 12(1|2)x isn't honoring 'existing' configuration

    Details

    • Type: Bug
    • Status: Closed (View workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects versions: 1.4.18
    • Fix versions: 1.4.18
    • Components: WebLogic
    • Labels:
      None

      Description

      When using following maven configuration, Cargo is overriding the existing domain with a new one. Previously defined configuration is then gone.

      <plugin>
        <groupId>org.codehaus.cargo</groupId>
        <artifactId>cargo-maven2-plugin</artifactId>
        <version>1.4.18-SNAPSHOT</version>
        <executions>
          <execution>
            <id>start-container</id>
            <phase>pre-integration-test</phase>
            <goals>
              <goal>start</goal>
            </goals>
          </execution>
          <execution>
            <id>stop-container</id>
            <phase>post-integration-test</phase>
            <goals>
              <goal>stop</goal>
            </goals>
          </execution>
        </executions>
        <configuration>
          <container>
            <type>installed</type>
            <containerId>weblogic121x</containerId> <!-- using 'weblogic122x' happens the same -->
            <home>${runtimeHome}</home>
          </container>
          <configuration>
            <type>existing</type>
            <home>${domainHome}</home>
            <properties>
              <cargo.servlet.port>${weblogic.http.port}</cargo.servlet.port>
              <cargo.weblogic.administrator.user>${weblogic.user}</cargo.weblogic.administrator.user>
              <cargo.weblogic.administrator.password>${weblogic.password}</cargo.weblogic.administrator.password>
              <cargo.weblogic.bea.home>${middlewareHome}</cargo.weblogic.bea.home>
              <cargo.weblogic.server>AdminServer</cargo.weblogic.server>
              <cargo.jvmargs>-Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256m</cargo.jvmargs>
            </properties>
          </configuration>
        </configuration>
      </plugin>
      

      Output:

      [INFO] --- cargo-maven2-plugin:1.4.18-SNAPSHOT:start (start-container) @ camunda-qa-weblogic-runtime ---
      [INFO] [2.ContainerStartMojo] Resolved container artifact org.codehaus.cargo:cargo-core-container-weblogic:jar:1.4.18-SNAPSHOT for container weblogic121x
      [INFO] [talledLocalContainer] WebLogic 12.1.x starting...
      [INFO] [ngLocalConfiguration] Creating new WebLogic domain.
      [INFO] [talledLocalContainer] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
      [INFO] [talledLocalContainer] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
      [INFO] [talledLocalContainer]
      [INFO] [talledLocalContainer] Initializing WebLogic Scripting Tool (WLST) ...
      [INFO] [talledLocalContainer]
      [INFO] [talledLocalContainer] Welcome to WebLogic Server Administration Scripting Shell
      [INFO] [talledLocalContainer]
      [INFO] [talledLocalContainer] Type help() for help on available commands
      [INFO] [talledLocalContainer]
      [INFO] [talledLocalContainer] Loading domain template.
      [INFO] [talledLocalContainer] Configuring domain and resources.
      [INFO] [talledLocalContainer] Writing domain.
      

      Expected behavior:

      • Cargo is honoring the existing domain configuration and just starts the server and deploys the deployables

        Attachments

          Activity

            People

            • Assignee:
              alitokmen S. Ali Tokmen
              Reporter:
              hawky-4s- Christian Lipphardt (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: