+++ This bug was initially created as a clone of Bug #820650 +++ Description of problem: I deployed a standalone web application on JBossAS 5 using JON (create child>web application). When i redeploy the same war (content>new>upload new package), original file in jBoss deploy directory is renamed and application is unreachable using original URL. Version-Release number of selected component (if applicable): Version: 3.1.0.GA Build Number: 07775cb:4ccefd7 How reproducible: always Steps to Reproduce: 1.deploy a new standalone web application on JBoss: select inventory on JBoss resource, than create child>web application 2.redeploy the same war: go to content>new>upload new package (see newPackageScreenshot.png) Actual results: original file helloworld.war in jboss-eap-5.1/jboss-as/server/default/deploy was renamed to helloworld.war-6204127540627021664 Package name shown on portal is correct (see historyScreenshot.png and deployedScreenshot.png) Expected results: Only version is updated
The AS5 deployer uses the file name as-is to determine the name of the app to be updated/deployed. Instead of adding the random UUID to the archive to be deployed, add the random UUID to a temp folder name and then download content there (leaving the file name unchanged). This issue has been fixed for both farmed and non-farmed deployments. release/jon3.1.x branch commits: http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commit;h=28f5c74ec24267eecf6ffe1e36a01a012e5c7198 http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commit;h=7b36fe4ad315679ea2e66431bbe5067037e1d539
Moving to ON_QA since this is included in the CR2 build.
Verified on 3.1.0.CR3 for both farmed and non-farmed deployments. For farmed deployment also verified that update doesn't result in non-farmed deployment (Bug 646631)