Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-20376

Deploy --force option not working with jboss-cli of WildFly 32

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • 32.0.1.Final, 35.0.0.Beta1
    • CLI
    • None

      With WildFly 27 I used the following command for updating a deployed and running app 'MyApp-1.0.0.war'  to new version 1.0.1
       
      ./jboss-cli.sh --connect --command="deploy MyApp-1.0.1.war --runtime-name=MyApp.war --force"
       
      The --force option led to replacing the the deployment with the new updated WAR file.
       
      The same command now fails with WildFly 32.0.1 with the following error.
      WFLYSRV0205: There is already a deployment called MyApp-1.0.1.war with the same runtime name MyApp
       
      Please note that even the error message is wrong. There is no deployment 1.0.1 in WF but the old 1.0.0

              rhn-cservice-bbaranow Bartosz Baranowski
              cwinkler29 Christian Winkler (Inactive)
              Bartosz Baranowski
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: