Unanswered question

Load Generator Connection is Busy

Before start the test Load generator connection is available after start the test or check Virtual user with specific load generator's then the connection is Busy.

We are getting below error in Load generator error log

Jul 08, 2019 10:30:51 PM org.glassfish.tyrus.container.jdk.client.ClientFilter processError
SEVERE: Connection error has occurred
java.io.IOException: An established connection was aborted by the software in your host machine
at sun.nio.ch.WindowsAsynchronousSocketChannelImpl.read0(Native Method)
at sun.nio.ch.WindowsAsynchronousSocketChannelImpl.access$700(WindowsAsynchronousSocketChannelImpl.java:43)
at sun.nio.ch.WindowsAsynchronousSocketChannelImpl$ReadTask.run(WindowsAsynchronousSocketChannelImpl.java:511)
at sun.nio.ch.WindowsAsynchronousSocketChannelImpl.implRead(WindowsAsynchronousSocketChannelImpl.java:657)
at sun.nio.ch.AsynchronousSocketChannelImpl.read(AsynchronousSocketChannelImpl.java:276)
at sun.nio.ch.AsynchronousSocketChannelImpl.read(AsynchronousSocketChannelImpl.java:297)
at java.nio.channels.AsynchronousSocketChannel.read(AsynchronousSocketChannel.java:420)
at org.glassfish.tyrus.container.jdk.client.TransportFilter._read(TransportFilter.java:283)
at org.glassfish.tyrus.container.jdk.client.TransportFilter.access$100(TransportFilter.java:78)
at org.glassfish.tyrus.container.jdk.client.TransportFilter$4.completed(TransportFilter.java:301)
at org.glassfish.tyrus.container.jdk.client.TransportFilter$4.completed(TransportFilter.java:283)
at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
at sun.nio.ch.Invoker$2.run(Invoker.java:218)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Thanks in Advance,

CHINNIKRISHNA REDDY B.
CHINNIKRISHNA REDDY B.

CHINNIKRISHNA REDDY B.

Level
1
163 / 750
points

Answers

Nouredine A.
Nouredine A.

Nouredine A.

Level
4
5000 / 5000
points
Team

I'm not sure to understand. What is exactly your issue? The agent is green before starting your check VU but when you start it the color changes to yellow meaning that the LG is busy. This is a normal behavior.

The stack trace you copied/paste is not related to LG.

CHINNIKRISHNA REDDY B.
CHINNIKRISHNA REDDY B.

CHINNIKRISHNA REDDY B.

Level
1
163 / 750
points

Hi Nouredine,

Once start check virtual user in specific LG's we are getting below error message. (LG's Signal is Yellow colour)

com.neotys.nl.controller.q.d.o: Load generator ip-xxx-xxx-xxx-xxx.us-west-1.compute.internal:7100 unavailable
at com.neotys.nl.controller.q.d.d.a(d.java:478)
at com.neotys.nl.controller.q.d.d.a(d.java:145)
at com.neotys.nl.controller.q.d.c.call(c.java:129)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Stijn S.
Stijn S.

Stijn S.

Level
0
23 / 100
points

We do see similar messages apearing in our log files. We run with NeoLoad 6.6 in NoGui way.

Nouredine A.
Nouredine A.

Nouredine A.

Level
4
5000 / 5000
points
Team

@CHINNIKRISHNA REDDY B. the error you mention happens when the controller is not able to communicate with the LG after you started your checkvu. This error is a consequence of another issue like the LG took too much time to start (there's 20s timeout) or it did not start at all. If that issue is random then the former is most likely the issue.

When you start your checkvu check on your LG the processes and if there's a "java.exe" that is starting. If yes check any other processes that could use CPU like antivirus which could slow down the starting of the LG. You can also increase the timeout in the agent.properties file of the LG.

The fact that it's a yellow color is normal since it is changed as soons as you hit the play button so nothing abnormal here.