[jboss-jira] [JBoss JIRA] Updated: (AS7-987) deployed marker is not removed if I change web.xml to something invalid

Andre Dietisheim (JIRA) jira-events at lists.jboss.org
Fri Jun 10 06:33:59 EDT 2011


     [ https://issues.jboss.org/browse/AS7-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated AS7-987:
---------------------------------

    Steps to Reproduce: 
# make sure you have an as7 running in standalone mode
# copy an artifact in exploded manner to the deployment folder (ex. bogus.war - deployed as a folder)
# make sure it's started by checking if there's a .deployed (ex. bogus.war.deployed) marker
# change the web.xml to something invalid (I added an "!" to the closing tag of <display-name>
# trigger it's restart by creating a .dodeploy marker (ex. bogus.war.dodeploy)
# Accessing your app by browser (http://localhost:8080/bogus) shows you that the deployment was stopped.

Result:
You still have a .deployed marker in the deployment folder. (the .dodeploy marker was removed by the scanner)

In the upcoming steps things get even more weird:

# change the web.xml to something valid again
# trigger its redeployment by creating a .dodeploy marker
# make sure you can access your app by browser

Result:
The deployment folder now has a .failed marker even though the deployment seems to be running.

  was:
# make sure you have an as7 running in standalone mode
# copy an artifact in exploded manner to the deployment folder (ex. bogus.war - deployed as a folder)
# make sure it's started by checking if there's a .deployed (ex. bogus.war.deployed) marker
# change the web.xml to something invalid (I added an "!" to the closing tag of <display-name>
# trigger it's restart by creating a .dodeploy marker (ex. bogus.war.dodeploy)
# Accessing your app by browser (http://localhost:8080/bogus) shows you that the deployment was stopped.

Result:
You still have a .deployed marker in the deployment folder. (the .dodeploy marker was removed by the scanner)

In the upcoming steps things get even more weird:

# change the web.xml to something valid again
# trigger its redeployment by creating a .dodeploy marker
# make sure you can access your app by browser

Result:
The deployment folder now has a .failed marker even though the deployment seems running.



> deployed marker is not removed if I change web.xml to something invalid
> -----------------------------------------------------------------------
>
>                 Key: AS7-987
>                 URL: https://issues.jboss.org/browse/AS7-987
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 7.0.0.Beta3
>         Environment: JBoss 7 Beta3 and JBoss 7 Beta4 (TRUNK aka master)
>            Reporter: Andre Dietisheim
>


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list