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

[admin-console] jboss-as-5 plugin: problems with deploying an application with an unmet dependency

    XMLWordPrintable

Details

    • Hide

      1) Log-in to the Admin Console (admin-console)
      2) Deploy missingdep.war

      The deployment will fail to deploy due to the missing dependency.

      Show
      1) Log-in to the Admin Console (admin-console) 2) Deploy missingdep.war The deployment will fail to deploy due to the missing dependency.
    • Workaround Exists
    • Hide

      Deploy applications or resources manually by dropping them into the deploy directory.

      Show
      Deploy applications or resources manually by dropping them into the deploy directory.
    • Low
    • Hide
      When an application was deployed using the admin-console (Profile Service API), the application deployment was removed if it failed to start. The application could not be redeployed using the admin-console because the deployment was removed when deployment or startup failures occurred. The fix forces the Admin Console to allow application or resource deployment, even if the deployment fails to start. This functionality allows for situations where the user expects an application will not start due to dependency issues or HA singleton configuration, but still requires the deployment to remain on the EAP server.
      Show
      When an application was deployed using the admin-console (Profile Service API), the application deployment was removed if it failed to start. The application could not be redeployed using the admin-console because the deployment was removed when deployment or startup failures occurred. The fix forces the Admin Console to allow application or resource deployment, even if the deployment fails to start. This functionality allows for situations where the user expects an application will not start due to dependency issues or HA singleton configuration, but still requires the deployment to remain on the EAP server.
    • Documented as Resolved Issue
    • ASSIGNED

    Description

      Description of problem:
      When deploying an application with an unmet dependency via admin console
      (Profile Service API):

      Admin console reports an error in deployment
      Application is not copied to deploy/ (or rather it seems that it is copied,
      but then deleted)
      Application does not show up in deployed applications in admin console
      Application DOES show up in JMX console, for example:

      J2EEApplication=null,J2EEServer=Local,j2eeType=WebModule,name=test.war

      An unmet dependency is NOT an error.
      Expected behavior:

      There shouldn't be an error (warning at most).
      Application should be copied to deploy/.
      Application should show up as a deployed application (where it could be
      undeployed).

      Why does the application still show up in JMX console but not in deploy/?
      It looks like the profile service assumes an error starting the application
      means
      it was never deployed, and doesn't undeploy before removing it from deploy/?

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. JBPAPP-6766 [admin-console] Component upgrade to Embedded JOPR release tag EmbJopr_1_3_4_SP5

          • 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

              rhn-support-loleary Larry O'Leary
              rhn-support-loleary Larry O'Leary
              Jared Morgan Jared Morgan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: