Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-2698

Admin Console: EAR/WAR deployment status not always updated

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.1.1
    • EAP 5.0.0.CR3, EAP_EWP 5.1.0
    • Consoles, Profile Service
    • None

    • jdk1.6.0_14
      32bit Fedora 10

    • Hide
      A bug in the Profile service caused the status of deployments to be reported incorrectly if they are started and stopped very quickly. This bug is still present. However, modifications have been made to the console to work around this by updating the status after a short delay, or after the page is refreshed. In normal usage, the status is shown as expected.
      Show
      A bug in the Profile service caused the status of deployments to be reported incorrectly if they are started and stopped very quickly. This bug is still present. However, modifications have been made to the console to work around this by updating the status after a short delay, or after the page is refreshed. In normal usage, the status is shown as expected.
    • Documented as Resolved Issue

    Description

      Access Admin console
      -> Web Application (WAR)s
      -> Add a new resource -> add sample.war (simple war example from tomcat): Deploy Exploded = no, Deploy Farmed = no (notice it can be accessed at localhost:8080/sample)
      -> in Admin console WARS, click sample.war -> Control -> Stop
      -> go back to Web Application (WAR)s, notice the status is DOWN (which it is if you check)
      -> sample.war -> Control -> Start
      -> go back to Web Application (WAR)s -> sample.war
      Status is DOWN still and stays like that even though its up and working

      Status stays the same even if you close the Admin Console. Only way to get it to update correctly is to apply another control action to another WAR ex) stop/restart jmx-console.war

      Attachments

        1. JBPAPP-2698.patch
          1 kB
        2. rhq-JBPAPP-2698.patch
          3 kB
        3. rhq-JBPAPP-2698v2.patch
          2 kB
        4. sample.war
          4 kB

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-2422 AS Console (Embedded Jopr) Bugs (tracking issue)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-3250 EAR deployment not always updated in admin console

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-5157 EAR application flagged as being unavailable in the admin-console

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              ozizka_jira Ondrej Zizka (Inactive)
              bshim_jira Brian Shim (Inactive)
              Misty Stanley-Jones Misty Stanley-Jones (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: