Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-12643

Deployment to EAP 5.1 does not work after stopping and starting the deployer using JMX

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate Issue
    • Affects Version/s: 4.0.0.Alpha1
    • Fix Version/s: LATER
    • Component/s: jmx
    • Labels:
      None
    • Environment:

      JBDS 6.0.0.Alpha1 H25

    • Steps to Reproduce:
      Hide

      1. Add EAP 5.1.2 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

      Show
      1. Add EAP 5.1.2 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

      Description

      (This issue was discovered by rawagner and I was able to reproduce it myself.)
      If you disable and then enable again the deployment on an EAP 5.1 server using JMX and then try to deploy something, it doesn't get deployed.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  rob.stryker Rob Stryker
                  Reporter:
                  mmalina Martin Malina
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: