GlassFish Server 3.1.x Reports LoadRequestCommand Timed Out Error for Replicated Web Application.
(Doc ID 1678700.1)
Last updated on MARCH 01, 2019
Applies to:Oracle GlassFish Server - Version 3.1.2 and later
Information in this document applies to any platform.
On Oracle GlassFish Server version 3.1.2.x, when attempting to stress test a GlassFish web application with a High Availability (HA) session enabled the following error occurs:
"WARNING|oracle-glassfish3.1.2|org.shoal.ha.cache.command.load_request|_ThreadID=xxxx;_ThreadName=http-thread-pool-xxx(93);|LoadRequestCommand timed out while waiting for result java.util.concurrent.TimeoutException|" as seen below:
The issue seems to happen when stress testing an HA enabled web application on a GlassFish cluster (containing > 1 node). When this error happens, the session being accessed fails to be retrieved and lost.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document