[GLASSFISH-18990] [PERF] JServlet2 HTTP/Servlet micro benchmark using in-memory session replication shows Timeout Exceptions Created: 10/Aug/12  Updated: 20/Dec/16  Resolved: 03/Dec/12

Status: Closed
Project: glassfish
Component/s: failover
Affects Version/s: 4.0_dev
Fix Version/s: None

Type: Bug Priority: Major
Reporter: deep_singh Assignee: Mahesh Kannan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Intel(R) Xeon(R) 8-CPU E5450 @ 3.00GHz 32GB
Linux 2.6.18-164.el5xen #1 SMP Thu Sep 3 04:41:04 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux



When running Web micro benchmark configured to use session replication among two instances of glassfish 4.0, getting a lot of warnings with timeout exception after a few minutes of starting performance test:

[#|2012-08-02T23:15:26.497-0700|WARNING|44.0|org.shoal.ha.cache.command.load_request|_ThreadID=106;_ThreadName=Thread-2;|LoadRequestCommand timed out while waiting for result java.util.concurrent.TimeoutException|#]

There are no other errors/exceptions in log files to indicate source of this or any other problem.

Comment by deep_singh [ 24/Aug/12 ]

This issue is resolved with integration of Grizzly 2.2.13 in Glassfish 4.0 b49 . The bug was due to wrong value for cookie which tracks version number for a replicated session. With the bug fix, the glassfish regression between Glassfish 3.1.2 and Glassfish 4.0 has come down from 44% (in b48) to 11% (in b49; as reported by Alacrity).

Generated at Thu Mar 30 02:45:37 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.