A micro-service reference test application for model extraction, cloud management, energy efficiency, power prediction, single- and multi-tier auto-scaling
Everytime I run the TeaStore locally and create load using JMeter, I get errors both from the JMeter results and also in the Kieker logs. This is annoying when trying to analyze the Kieker logs. The only workaround if to wait for ~10 minutes, then the problem sometimes disappears (but I'm not completely sure about the time, and this is obviously very time-consuming to test).
When looking at the JMeter GUI, the problem seems to appear randomly, sometimes when GET http://localhost:8080/tools.descartes.teastore.webui/ is called, sometime when POST http://localhost:8080/tools.descartes.teastore.webui/cartAction is called.
Is there some way to tell that the startup has ended? I tried to get the container logs using for container in $(docker ps | grep -v "CONTAINER ID" | awk '{print $1}'); do docker logs $container &> $container.txt; done, but even if situations where the logs had their final size, the error still occured.
Everytime I run the TeaStore locally and create load using JMeter, I get errors both from the JMeter results and also in the Kieker logs. This is annoying when trying to analyze the Kieker logs. The only workaround if to wait for ~10 minutes, then the problem sometimes disappears (but I'm not completely sure about the time, and this is obviously very time-consuming to test).
I'm starting the TeaStore using
and create the load using
java -jar /home/reichelt/Programme/apache-jmeter-5.5/bin/ApacheJMeter.jar -t examples/jmeter/teastore_browse_nogui.jmx -Jhostname localhost -Jport 8080 -JnumUser 2 -n
When looking at the JMeter GUI, the problem seems to appear randomly, sometimes when
GET http://localhost:8080/tools.descartes.teastore.webui/
is called, sometime whenPOST http://localhost:8080/tools.descartes.teastore.webui/cartAction
is called.Is there some way to tell that the startup has ended? I tried to get the container logs using
for container in $(docker ps | grep -v "CONTAINER ID" | awk '{print $1}'); do docker logs $container &> $container.txt; done
, but even if situations where the logs had their final size, the error still occured.