Project

General

Profile

Bug #11902

load-test MSA with maxMsaSessionAge=1

Added by Constantin Asofiei about 13 hours ago. Updated about 13 hours ago.

Status:
New
Priority:
Normal
Assignee:
Eduard Soltan
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#1 Updated by Eduard Soltan about 13 hours ago

  • Assignee set to Eduard Soltan

#2 Updated by Constantin Asofiei about 13 hours ago

In a project, I set maxMsaSessionAge to 10, but this value is in milliseconds (and I assumed it was seconds).

But, with 10ms, each MSA session got destroyed immediately - this showed some weird stacktraces, where database connections got lost.

We need some stress testing with maxMsaSessionAge=1 with some complex scenarios, where the databases are not with load_at_startup=true, but with database-connections - see the setup for #11871

Also available in: Atom PDF