HTTP Sessions Created In A ServletRequestListener Do Not Expire In Oracle Glassfish Server 3.1.1
Last updated on NOVEMBER 05, 2016
Applies to:Oracle GlassFish Server - Version: 3.1 to 3.1.1 - Release: 3.1 to 3.1
Information in this document applies to any platform.
The only way to see if this problem is occurring is to examine some of the metadata in the HTTP Session object itself, principally the session's last access time and its max idle time, and compare that to the current wall clock time. This problem is present if:
lastAccessedTime() + (maxInactiveInterval() * 1000) < currentTimeMillis()
Here the first two method calls are available from the HttpSession object, and the last from the System object. Note the max inactive interval is in seconds, and needs to be converted to milliseconds to be able to used correctly in the above comparison.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms