[jbosstools-issues] [JBoss JIRA] (JBIDE-16950) Very frequently, webapps are being undeployed right after being deployed

Martin Malina (JIRA) issues at jboss.org
Fri Apr 4 07:01:14 EDT 2014


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

Martin Malina commented on JBIDE-16950:
---------------------------------------

I now understand why I couldn't reproduce it last time I tried (today I can). 
I used these steps:
1. Start AS 7
2. Create dynamic project
3. Deploy the project

In this scenario, the duplicate scanner is not added at server start.
When I tried again, but this time the project was already created before server start (so effectively 1. and 2. were switched),
I could then reproduce the issue - after server start, the duplicate deployment scanner was added.
{code}
11:57:20,349 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory C:\JBDS\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\deployments
{code}
This is probably because the bug had something to do with the mechanism that ensures each module has a deployment scanner that will notice it once deployed - so no module in workspace means no problem.

(Note that all this time I've been using Beta1 B79 which does not contain respin-a fixes such as JBIDE-16866. But then I tried the latest build B82 and the result was exactly the same as described above. So no difference was observed between the two builds.)
                
> Very frequently, webapps are being undeployed right after being deployed
> ------------------------------------------------------------------------
>
>                 Key: JBIDE-16950
>                 URL: https://issues.jboss.org/browse/JBIDE-16950
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Beta1
>         Environment: Win 7-64, JDK 7, AS 7.1.1, WildFly 8.0.0
>            Reporter: Fred Bricon
>            Assignee: Rob Stryker
>            Priority: Blocker
>              Labels: respin-b
>             Fix For: 4.2.0.Beta1
>
>
> I'm experiencing this issue where, after doing a full publishing, the deployed webapp is being undeployed right after being deployed.
> See http://screencast.com/t/JmwA0TlBrDWX
> The most reliable way (even though it's not 10% of the time) to reproduce the issue is to deploy a webapp to AS 7.1.1 or WF8, then remove it from the server, deploy it back. That's when the problem occurs : 
> {noformat}
> 14:13:45,356 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "dontundeployme.war" (runtime-name: "dontundeployme.war")
> 14:13:45,485 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /dontundeployme
> 14:13:45,683 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "dontundeployme.war" (runtime-name : "dontundeployme.war")
> 14:13:50,708 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017535: Unregistered web context: /dontundeployme
> 14:13:50,730 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment dontundeployme.war (runtime-name: dontundeployme.war) in 23ms
> 14:13:50,999 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018558: Undeployed "dontundeployme.war" (runtime-name: "dontundeployme.war")
> 14:13:56,004 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found dontundeployme.war in deployment directory. To trigger deployment create a file called dontundeployme.war.dodeploy
> {noformat}
> Also, pretty quite frequently, deployment just fails (but I haven't been able to figure out a decisive pattern yet) as the server thinks deployments are duplicates (see screencast)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list