IOExceptions thrown after HTTP/2 stream is closed by client

[wtlucy]

A remote client might close a HTTP/2 stream for a number of reasons - the response might be taking too long, or the client might just decide that it no longer needs a resource. In HTTP/1.1, a remote client would just close the connection to accomplish the same goal.

Currently, as a response is being written out in Liberty, the HTTP/1.1 connection close is handled differently than HTTP/2 stream closure. In the HTTP/2 case, a java.io.IOException: com.ibm.ws.http2.upgrade.H2Exception: stream was already closed! error is thrown - which can lead to multiple errors being logged such as SRVE0315E and SRVE0777E. In the HTTP/1.1 case, the IOExceptions are configurable.