Jetspeed 2
  1. Jetspeed 2
  2. JS2-196

Stop trying when hot deployment fails

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-M1
    • Fix Version/s: 2.0-dev/cvs, 2.0-M2
    • Component/s: None
    • Labels:
      None
    • Environment:
      Windows 2000, JBoss 4.0.1, Jetspeed-2 M1

      Description

      The deployment of the pam.war fails during start-up, so the war is un-deployed, and a deploy is retried, which also fails. Unless the war file is removed from the file system, this process is iterated infinitely.

      The process follows these steps:
      1. The ScannerThread detects a new war file in the deploy directory.
      2. The Portlet war file is loaded.
      3. The Portlet war file is deployed.
      4. Error occurs during deployment.
      5. The Portlet war file is un-deployed.
      6. The Portlet file remains in the deploy dir to be detected when the ScannerThread wakes-up again.

        Activity

        Hide
        Ate Douma added a comment -

        See http://issues.apache.org/jira/browse/JS2-210.
        Deployment has been completely rewritten.

        Show
        Ate Douma added a comment - See http://issues.apache.org/jira/browse/JS2-210 . Deployment has been completely rewritten.

          People

          • Assignee:
            Unassigned
            Reporter:
            Legolas Greenleaf
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development