Sporadic HTTPS Response Corruption on GlassFish 2.1.1.23 and 2.1.1.24 (Doc ID 1957918.1)

Last updated on JANUARY 29, 2025

Applies to:

Symptoms

Very sporadically some responses to requests over HTTPS return invalid content, potentially with stale data from another request.  The problem is not seen with HTTP requests, only HTTPS and appears to be triggered when large volumes of data are being returned to a client and the client exits before all the data has been read.  This is very infrequent and therefore potentially very difficult to detect.  One way is to have a health-checking client that makes a request to a non-existent servlet or jsp over HTTPS.  The response to this should return a HTTP 404 error page, but if a HTTP 200 or other data is returned then the problem has been encountered.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.