Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exceptions when running with the newest locust (2.25.0) #43

Open
zettelmj opened this issue Apr 16, 2024 · 6 comments
Open

Exceptions when running with the newest locust (2.25.0) #43

zettelmj opened this issue Apr 16, 2024 · 6 comments

Comments

@zettelmj
Copy link

zettelmj commented Apr 16, 2024

Hi,

I am using the newest version of locust4j with the newest version of locust (2.25.0).
I am seeing a large number of exceptions like:

java.lang.IllegalArgumentException: null
  at java.base/java.util.concurrent.ThreadPoolExecutor.setMaximumPoolSize(Unknown Source)
  at com.github.myzhan.locust4j.runtime.Runner.startSpawning(Runner.java:217)
  at com.github.myzhan.locust4j.runtime.Runner.onSpawnMessage(Runner.java:291)
  at com.github.myzhan.locust4j.runtime.Runner.onMessage(Runner.java:336)
  at com.github.myzhan.locust4j.runtime.Runner.access$600(Runner.java:28)
  at com.github.myzhan.locust4j.runtime.Runner$Receiver.run(Runner.java:413)
  at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
  at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
  at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
  at java.base/java.lang.Thread.run(Unknown Source)

any ideas what could cause this/Hints how to debug the Issue?

Thank you
Jens

@myzhan
Copy link
Owner

myzhan commented Apr 17, 2024

How can I reproduce this issue?

@zettelmj
Copy link
Author

It seems to happen most frequently when a run is stopped. I will comb more thorough the logs later

@zettelmj
Copy link
Author

I went through the logs. To give particular example:
I can see the worker coming online. Master node then logs out that the worker is available. Approximately 3 microseconds after spawning jobs (1 user at 1.0 spawn rate) the above stack trace can be observed (and is repeated every seconds till the job is stopped).

I forgot to mention that the Task itself is written in Kotlin (Version 1.9.22) and is running on temurin 21 latest

@myzhan
Copy link
Owner

myzhan commented Apr 17, 2024

I can't reproduce while spawning jobs(1 user at 1.0 spawn rate) using OpenJDK.

@zettelmj
Copy link
Author

Is there a specific class I could set logging to tracing on or something similar that would allow a bit more insights?

@myzhan
Copy link
Owner

myzhan commented Apr 18, 2024

You can try to print out the messages sent by locust here,

private void onMessage(Message message) {

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants