[jbosstools-issues] [JBoss JIRA] (JBIDE-12156) Apps are not deployed after EAP 6 restart

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700704#comment-12700704 ] 

Martin Malina commented on JBIDE-12156:
---------------------------------------

To be sure this has nothing to do with JBDS/JBT, I tried this completely without our tools. What I did:
1. Unzip EAP 6.0 CR1
2. Start the server using ./standalone.sh
3. Copy exploded war in deployments: cp -R dynproj.war $JBOSS_HOME/standalone/deployments/
5. This told me I needed .dodeploy, so I did that: touch $JBOSS_HOME/standalone/deployments/dynproj.war.dodeploy
6. Stop server
7. Start server again using ./standalone.sh
8. dynproj.war is not deployed - this is in server log:
{code}
12:01:48,788 INFO  [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
{code}
                
> Apps are not deployed after EAP 6 restart
> -----------------------------------------
>
>                 Key: JBIDE-12156
>                 URL: https://issues.jboss.org/browse/JBIDE-12156
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.CR1
>         Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar
> JBoss EAP 6 CR1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 3.3.1
>
>
> Found this when verifying JBIDE-11509.
> When you have EAP 6 up and running with an app deployed (any app, e.g. a simple dynamic web project) and then you stop and start the server, the app won't be deployed anymore. This is specific to EAP. In AS 7.1.1 the app gets deployed at the server start.
> With EAP 6 CR1 you will be shown this in the server log:
> {code}
> 15:46:25,828 INFO  [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
> {code}
> I understand this is an issue of EAP, but we need to decide if we can do something to overcome this limitation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira