[directory-fortress-core] branch master updated: + troubleshooting jmeter out of memory

[sm...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

smckinney pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/directory-fortress-core.git


The following commit(s) were added to refs/heads/master by this push:
     new ca95b3b4 + troubleshooting jmeter out of memory
ca95b3b4 is described below

commit ca95b3b45e6feafab2a4558b0f1f51310c149c25
Author: Shawn McKinney <sm...@symas.com>
AuthorDate: Tue Jul 4 07:55:28 2023 -0500

    + troubleshooting jmeter out of memory
---
 README-LOAD-TESTING.md | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/README-LOAD-TESTING.md b/README-LOAD-TESTING.md
index 37fa776e..e2a440f6 100644
--- a/README-LOAD-TESTING.md
+++ b/README-LOAD-TESTING.md
@@ -378,5 +378,30 @@ Sample error
 [INFO] Shutdown detected, destroying JMeter process...
 ```
 ____________________________________________________________________________________
+
+##### C. jmeter tests hang
+
+Observation: 
+When running tests that consume lots of memory, e.g. using many threads and/or enabling REST, the process hangs.
+Jmeter and log4j logs stop outputing. The machine's otherwise unaffected. LDAP and/or HTTP servers are responsive.
+Root Cause:
+Most likely jmeter has run out of memory. Unfortunately, when this happens, 
+an error is not reported. The process hangs and stops responding.
+
+Remedy:
+Edit the project's pom.mxl. Goto the loadtest profile. Increase the memory allocation, e.g. 2048 (2GB):
+```xml
+<profile>
+   <id>loadtest</id>
+   <build>
+    ...
+      <jMeterProcessJVMSettings>
+         <xms>2048</xms>
+         <xmx>2048</xmx>
+      </jMeterProcessJVMSettings>
+    ...
+   </build>
+</profile>
+```
  
 #### END OF README