Details

    • Type: Bug Bug
    • Status: Closed (View Workflow)
    • Priority: Minor Minor
    • Resolution: Migrated to another ITS
    • Affects Version/s: EWS 1.0.1, EWS 1.0.0.GA
    • Fix Version/s: TBD EWS
    • Labels:
      None
    • Environment:
      all
    • Affects:
      Release Notes
    • Similar Issues:
      Show 8 results 

      Description

      When a deployment or a virtual host is stopped in tomcat5, an access attempt is replied to with:
      HTTP Status 503 - This application is not currently available

      When a deployment is stopped in tomcat 6, it replies with 404.
      When a virtual host is stopped in tomcat 6 it replies with 400 Bad Request.

      Tomcat 5 behavior seems more consistent. Let me know if tomcat community has decided for such change.

        Gliffy Diagrams

          Activity

          Hide
          Jean-Frederic Clere added a comment -

          It is not "fixed" in the upstream code.
          Did someone create a ASF bugxilla corresponding to that?

          Show
          Jean-Frederic Clere added a comment - It is not "fixed" in the upstream code. Did someone create a ASF bugxilla corresponding to that?
          Hide
          Aleksandar Kostadinov added a comment -

          Tomcat 6:
          https://issues.apache.org/bugzilla/show_bug.cgi?id=51116

          Tomcat 5:
          I'm not sure about this one.

          from http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

          10.5.4 503 Service Unavailable

          The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.

          So 503 for an app down for maintenance looks sane to me. In any case I have filed a bug:
          https://issues.apache.org/bugzilla/show_bug.cgi?id=51117

          Show
          Aleksandar Kostadinov added a comment - Tomcat 6: https://issues.apache.org/bugzilla/show_bug.cgi?id=51116 Tomcat 5: I'm not sure about this one. from http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html 10.5.4 503 Service Unavailable The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response. So 503 for an app down for maintenance looks sane to me. In any case I have filed a bug: https://issues.apache.org/bugzilla/show_bug.cgi?id=51117
          Show
          Jean-Frederic Clere added a comment - The right patch is https://issues.apache.org/bugzilla/attachment.cgi?id=26626
          Hide
          Jean-Frederic Clere added a comment -

          I have marked 51116 as a duplicated of 50734 in bugzilla and tested future 6.0.33 it is fixed there.

          Show
          Jean-Frederic Clere added a comment - I have marked 51116 as a duplicated of 50734 in bugzilla and tested future 6.0.33 it is fixed there.
          Hide
          RH Bugzilla Integration added a comment -

          This issue has been migrated to Bugzilla bug 899238. Please note that this JIRA issue has been closed as part of the migration and therefore you will need to check the Bugzilla issue to find the current status.

          Show
          RH Bugzilla Integration added a comment - This issue has been migrated to Bugzilla bug 899238 . Please note that this JIRA issue has been closed as part of the migration and therefore you will need to check the Bugzilla issue to find the current status.

            People

            • Assignee:
              David Knox
              Reporter:
              Aleksandar Kostadinov
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development