Re: Digest for ptgram24@googlegroups.com - 5 updates in 2 topics

10 views
Skip to first unread message

Lal Mani Kashyap

unread,
Jun 14, 2024, 1:44:45 AMJun 14
to ptgr...@googlegroups.com
I am getting this warning and using only regular expression extractor and JMeter-plugin xml formatter in script. Not using Xpath extractor.
Please help me how I can remove this warning in JMeter v5.6.2 .


From: ptgr...@googlegroups.com <ptgr...@googlegroups.com>
Sent: 13 June 2024 18:43
To: Digest recipients <ptgr...@googlegroups.com>
Subject: Digest for ptgr...@googlegroups.com - 5 updates in 2 topics
 

EXTERNAL: This message was sent from outside of Infogain. Please do not click links or open attachments unless you know the content is safe.

prabhakar singireddy <prabha.mu...@gmail.com>: Jun 12 09:48AM -0700

Hi team,
I am using the nongui mode of testing with the help of master and while
executing it threw out of memory exception and heap memory issue but is
solved after giving more heap size.
 
the main issue here is the memory usage is crossing above 90% even when
tried to run in local machine but still it is the same issue,
 
pls tell me if there is any way to solve this issue.
 
note: heap setting
if not defined HEAP (
rem See the unix startup file for the rationale of the following parameters,
rem including some tuning recommendations
set HEAP=-Xms21g -Xmx21g -XX:MaxMetaspaceSize=256m
) thanks & Regards, Prabhakar S.
prabhakar singireddy <prabha.mu...@gmail.com>: Jun 13 03:19AM -0700

Hi,
 
there are more heap files(.hprofs) getting generated, and the same script
is working fine with out any issue in memory and heaps.
the configuration used in other machine is
if not defined HEAP (
rem See the unix startup file for the rationale of the following parameters,
rem including some tuning recommendations
set HEAP=-Xms10g -Xmx10g -XX:MaxMetaspaceSize=256m
) Thanks.
 
On Wednesday, June 12, 2024 at 10:18:30 PM UTC+5:30 prabhakar singireddy
wrote:
 
DT <gli...@gmail.com>: Jun 13 03:44AM -0700

OutOfMemoryError
<https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/memleaks002.html>
Exception has many possible reasons and each particular occurrence requires
its own workaround or tuning on JMeter and/or operating system level
 
Yes, in the majority of cases it's lack of JVM Heap space, but it can also
be something connected with impossibility to allocate native memory due to
operating system limitations. So you need to inspect this .hprof file and
get to the bottom of the issue.
 
JMeter-only solution would be getting either more powerful machine or
another machine of the same specifications and running JMeter in
distributed mode
<https://www.blazemeter.com/blog/distributed-testing-in-jmeter>. In both
cases make sure to follow JMeter Best Practices
<https://jmeter.apache.org/usermanual/best-practices.html>
 
Also having large heap is not always a good idea, garbage collections
<https://www.oracle.com/webfolder/technetwork/tutorials/obe/java/gc01/index.html>
will occur less often but will take more time resulting in "chainsaw" load
pattern
 
On Thursday, June 13, 2024 at 12:19:30 PM UTC+2 prabha.mu...@gmail.com
wrote:
 
Sachin Sinkar <sachin....@gmail.com>: Jun 13 03:01AM -0700

Hi Team,
 
 
I have created a test plan for load testing a websocket based GPT chatbot.
I have set ramp-up period of 400 sec the test plan works well for 100
threads with no error but when I increased to 500 threads the WebSocket
request-response Samplers fails, it gives me below error.
 
Response code:Sampler error Response message:Sampler error:
java.lang.ClassCastException: class eu.luminis.websocket.PingFrame cannot
be cast to class eu.luminis.websocket.DataFrame
(eu.luminis.websocket.PingFrame and eu.luminis.websocket.DataFrame are in
unnamed module of loader org.apache.jmeter.DynamicClassLoader @548c4f57)
 
 
[image: plan.png]
 
[image: result.png]
 
Will you please suggest me a solution for the above error.
DT <gli...@gmail.com>: Jun 13 03:40AM -0700

It might indicate one of the following:
 
- The system under test is overloaded can cannot respond with a proper
WebSocket frame, it indicates defect connected with concurrency
- JMeter is overloaded and cannot properly parse responses/build
requests. In this case make sure to follow JMeter Best Practices
<https://jmeter.apache.org/usermanual/best-practices.html> and if the
issue still remains - consider finding another load generator machine and run
JMeter in distributed mode
<https://www.blazemeter.com/blog/distributed-testing-in-jmeter>

 
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to ptgram24+u...@googlegroups.com.

The information in this email is confidential and may be legally privileged. It is intended solely for the addressee and access to it by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken based on it, is strictly prohibited and may be unlawful.

Reply all
Reply to author
Forward
0 new messages