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

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • LATER
    • 4.0.0.Alpha1
    • jmx
    • None
    • 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.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-9973 Disable deployment scanner 2x, cannot resume

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          duplicates

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-11215 JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-13013 Deployment scanner in EAP5 works even if stopped via jmx

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              rob.stryker Rob Stryker (Inactive)
              exd-mmalina Martin Malina
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: