[jbosstools-issues] [JBoss JIRA] (JBIDE-13013) Deployment scanner in EAP5 works even if stopped via jmx

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-13013:
---------------------------------------

OK, I think I know why this happens. From JBIDE-11215 by Max:
{quote}
okey so here is how the tools work (in simplified form):
1) User changes files.
2) Server adapter tells server to stop scanning for changes in the directory we are copying to.
3) Server adapter copies files.
4) Server adapter tells server to start scanning for changes in the directory we are copying to
5) Server eventually sees the changes and redeploys/picksup the changes (depends on the kind of content, but thats unrelated to this I believe)
{quote}

So in the situation where you already stopped the scanner and then try to publish something this is what happens:
Step 2) stops the scanner - it was stopped already, but that's not a problem.
Step 4) starts the deployment scanner again (even if you intentionally stopped it).

In my opinion we don't really need to be able to stop the deployment scanner and leave it stopped - so I don't think this is something that needs testing. But I opened this JIRA to make sure it works as expected here. Also, we need to be aware that the test scenario we previously used cannot be used.
                
> Deployment scanner in EAP5 works even if stopped via jmx
> --------------------------------------------------------
>
>                 Key: JBIDE-13013
>                 URL: https://issues.jboss.org/browse/JBIDE-13013
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 4.0.0.Beta2
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.0.0.CR1
>
>
> With JBPAPP-9973 fixed I tried this scenario from JBIDE-12643 which should now work:
> {quote}
> 1. Add EAP 5.2.0.ER4 server
> 2. Create a dynamic web project (or whatever)
> 3. Start the server
> 4. Deploy your project
> ASSERT project deployed
> 5. Remove project
> ASSERT project undeployed
> 6. Go to MBean explorer and stop the deployer
>   From https://community.jboss.org/wiki/SmokeTestJBToolsServerSupport?prevContainerType=14
>   12) Open MBean Viewer,
>     a) note that the server can now be expanded,
>     b) under it are mbeans. browse down to jboss.deployment -> URL ->DeploymentScanner,
>     c) double-click DeploymentScanner, go to "Operations" page, click "stop" in viewer, click "stop" button on the right,
>     d) verify operation completes successfully
> 7. Repeat steps 4. and 5. - this time nothing will be deployed
> 8. Start the deployer again - see step 6
> 9. Repeat steps 4. and 5. - still no deployment - FAIL
> {quote}
> But it doesn't work - when you stop the deployment scanner (step 6) and try to deploy your project again, it will get deployed.
> I suspect that the publish operation checks if the deployment scanner is active and if it's not it will enable it again. If that's the case then this probably isn't a bug. But then we can no longer use that use case in any testing (i.e. disable deployment scanner and check that nothing can be deployed).

--
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