ICEfaces
  1. ICEfaces
  2. ICE-2121

ICEfaces AHS: NPE when logging the sent HTTP Response

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.6.1
          • Fix Version/s: 1.6.1
          • Component/s: None
          • Labels:
            None
          • Environment:
            ICEfaces Asynchronous HTTP Server 1.6.1
          • Workaround Exists:
            Yes
          • Workaround Description:
            Turn off DEBUG level logging for ICEfaces AHS

            Description

            When logging at DEBUG level for ICEfaces AHS it is possible that an NPE is thrown when trying to log the sent HTTP Response.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Jack Van Ooststroom added a comment -

              The fix for this issue is targeted for ICEfaces Asynchronous HTTP Server 1.6.1a.

              Show
              Jack Van Ooststroom added a comment - The fix for this issue is targeted for ICEfaces Asynchronous HTTP Server 1.6.1a.
              Hide
              Permalink
              Jack Van Ooststroom added a comment -

              When an invalid HTTP Request is received the ICEfaces Asynchronous HTTP Server tries to send an client error response indicating the error found in the HTTP Request. Because the HTTP Request contained an error it is not added to the Transaction object. When the HTTP Response is send back it tries to log the Request-URI of the HTTP Request. Because that is null an NullPointerException was thrown. I added a little check to see if the HttpRequest is null before retrieving the Request-URI from it. Marking this one as FIXED.

              Show
              Jack Van Ooststroom added a comment - When an invalid HTTP Request is received the ICEfaces Asynchronous HTTP Server tries to send an client error response indicating the error found in the HTTP Request. Because the HTTP Request contained an error it is not added to the Transaction object. When the HTTP Response is send back it tries to log the Request-URI of the HTTP Request. Because that is null an NullPointerException was thrown. I added a little check to see if the HttpRequest is null before retrieving the Request-URI from it. Marking this one as FIXED.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Jack Van Ooststroom
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: