abiy / distgatling Goto Github PK

follow the user-guide， i started server，but the page keep loading，i got a 404 error
for get https://unpkg.com/[email protected]/operators.js .so i can't open CM page now.

It would be nice to build gatling-rest in such a way that we can do npm install, pull required modules and package that into JAR rather than dynamically loading from the web. In this way we can provide immutable artifact which always would work in the same way. That would help to avoid situations when downstream repos are down, or latest version of module ports to alpha version (like https://unpkg.com/rxjs -> https://unpkg.com/[email protected])

Add a ReST path that outputs the following information from a given build number

Counts:
Total
OK
KO
KO%
Req/s

Response:
Min
50th Percentile
75th Percentile
95th Percentile
99the Percentile
Max
Mean
Std. Deviation

I've created Docker containers for the rest master and the agent. They can communicate but the rest master always seems to bind to the 172 Docker address, but the traffic is coming in on the 10, address and so the . This leads to the following error. Is there any configuration I can change to allow this agent to connect please?

2020-03-04 12:04:02.427 ERROR 9 --- [lt-dispatcher-2] akka.remote.EndpointWriter : dropping message [class akka.actor.ActorSelectionMessage] for non-local recipient [Actor[akka.tcp://[email protected]:2551/]] arriving at [akka.tcp://[email protected]:2551] inbound addresses are [akka.tcp://[email protected]:2551]

The distGatlingClient throws a NPE when there are missing properties from the config.yml file. This dumps the stacktrace to terminal. The NPEs should be caught and a meaningful message outputted for the error.

Currently, if a job fails, the website provides no further information as to why. There should be a mechanism to expose the logs of the failed run to allow for preliminary debugging instead of having to ssh into the box for solutions.

Hi,
i tried building your project inside a container to have a final slim master and worker container.
mvn clean package fails when executing test

Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [akka.actor.ActorSystem]: Factory method 'createActorSystemWithMaster' threw exception; nested exception is java.lang.ClassNotFoundException: javafx.util.Pair at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:189) at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588)

do you have any advise?

Any plans to support Kubernetes as a platform for deploying workers? I was thinking to contribute maybe to the project and provide possibility for dist gaitling to support Kubernetes to ramp-up workers on demand.

Frequently, resources are in period of contention requiring load tests to run in off peak hours. Allowing for a job to be submitted in the future would allow for people to setup load tests to run over night, or, if exhaustive testing is being down with a variety of configurations, sequence a set of load tests to be run over the course of several hours.

Currently, in order to submit a job as a JAR file, it requires to user to package the jar with all of its dependencies which leads to JAR files starting a 40MB because they have to package Scala and Gatling in them. Given that these are consistent dependencies in every JAR file, we should allow for the config.yml to specify what versions of these people are using and merge them with the JAR that is uploaded to decrease the network load required to setup a job.

Is it possible to use distGatling with gatling projects which are written with maven?

There is no file named gatling.sh in maven project, so confused how to edit the application.yml

When running perf tests with 2M+ requests, gatling-rest fails to merge reports from multiple workers. Works fine on smaller sets

https://github.com/coursier/coursier is a tool for resolving the transitive dependencies for a maven / ivy artifact. It would be good to support an artefact name (then resolve it) instead of requiring an uber jar... it can be very difficult to publish uber jars in many organisations.

Currently, If someone wants to use a JAR file to run their load tests, they need to use the DistGatling Client. It would be great to allow for the web UI to permit the upload of a JAR file.

If there is a failure in trying to load a JAR to the distGatling cluster via the shell script, the script still attempts to run the jar even though it doesn't exist. Relatedly, failures to upload a jar should output a useful log message instead of a stacktrace.

Master works fine. When I run the agent.sh, I am getting the below error

Message [akka.actor.Status$Failure] from Actor[akka://PerformanceSystem/system/transports/akkaprotocolmanager.tcp0/akkaProtocol-tcp%3A%2F%2FPerformanceSystem%40***...%3A2551-1#1419370574] to Actor[akka://PerformanceSystem/system/transports/akkaprotocolmanager.tcp0/akkaProtocol-tcp%3A%2F%2FPerformanceSystem%40...%3A2551-1#1419370574] was not delivered. [8] dead letters encountered. If this is not an expected behavior, then [Actor[akka://PerformanceSystem/system/transports/akkaprotocolmanager.tcp0/akkaProtocol-tcp%3A%2F%2FPerformanceSystem%40...%3A2551-1#1419370574]] may have terminated unexpectedly, This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
2021-11-21 06:26:31.049 WARN 5035 --- [lt-dispatcher-5] a.remote.transport.netty.NettyTransport : Remote connection to [null] failed with org.jboss.netty.channel.ConnectTimeoutException: connection timed out: /...***:2551
2021-11-21 06:26:33.820 INFO 5035 --- [lt-dispatcher-4] ctorRefProvider$RemoteDeadLetterActorRef : Message [akka.cluster.client.ClusterReceptionist$Internal$GetContacts$] from Actor[akka://PerformanceSystem/user/clusterClient#2136760599] to Actor[akka://PerformanceSystem/deadLetters] was not delivered. [9] dead letters encountered. If this is not an expected behavior, then [Actor[akka://PerformanceSystem/deadLetters]] may have terminated unexpectedly, This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.

This sis the command

/bin/bash agent.sh -Dakka.contact-points=:2551 -Dactor.port=2558 -Dserver.port=8090

Could you please help?

Currently, the last output from the distGatlingClient prior to exiting is to provide the following log line.
Job submitted. tracking info =>#detail/f1ce22b2-70af-442a-803d-d67226004bd5
As a small feature, it'd be nice if the host and port were pulled from the config.yml in order to fully populate this tracking page.

1. Run
   /bin/bash master.sh -Dmaster.port=<2551> -Dserver.port=<8080>
2. Open browser to GET http://localhost:8080/ to access the web page

Page not loading and error appears in browser console:

Error ​ columnNumber: 0 ​ fileName: "https://unpkg.com/[email protected]/dist/system.src.js" ​ lineNumber: 1460 ​ message: "Fetch error: 404 Not Found\n Instantiating https://unpkg.com/[email protected]/operators.js\n Loading https://unpkg.com/@angular/core/bundles/core.umd.js\n Loading http://localhost:8080/app/main.js\n Loading app" ​ originalErr: Error ​​ columnNumber: 13 ​​ fileName: "https://unpkg.com/[email protected]/dist/system.src.js" ​​ lineNumber: 1460 ​​ message: "Fetch error: 404 Not Found" ​​ stack: "fetchFetch/<@https://unpkg.com/[email protected]/dist/system.src.js:1460:13\nZoneDelegate.prototype.invoke@https://unpkg.com/zone.js/dist/zone.js:388:17\nZone.prototype.run@https://unpkg.com/zone.js/dist/zone.js:138:24\nscheduleResolveOrReject/<@https://unpkg.com/zone.js/dist/zone.js:872:29\nZoneDelegate.prototype.invokeTask@https://unpkg.com/zone.js/dist/zone.js:421:17\nZone.prototype.runTask@https://unpkg.com/zone.js/dist/zone.js:188:28\ndrainMicroTaskQueue@https://unpkg.com/zone.js/dist/zone.js:595:25\nn@https://unpkg.com/core-js/client/shim.min.js:8:31509\nR/<@https://unpkg.com/core-js/client/shim.min.js:8:31654\nt@https://unpkg.com/core-js/client/shim.min.js:7:26035\n" ​​ __proto__: Object { … } ​ stack: "fetchFetch/<@https://unpkg.com/[email protected]/dist/system.src.js:1460:13\nZoneDelegate.prototype.invoke@https://unpkg.com/zone.js/dist/zone.js:388:17\nZone.prototype.run@https://unpkg.com/zone.js/dist/zone.js:138:24\nscheduleResolveOrReject/<@https://unpkg.com/zone.js/dist/zone.js:872:29\nZoneDelegate.prototype.invokeTask@https://unpkg.com/zone.js/dist/zone.js:421:17\nZone.prototype.runTask@https://unpkg.com/zone.js/dist/zone.js:188:28\ndrainMicroTaskQueue@https://unpkg.com/zone.js/dist/zone.js:595:25\nn@https://unpkg.com/core-js/client/shim.min.js:8:31509\nR/<@https://unpkg.com/core-js/client/shim.min.js:8:31654\nt@https://unpkg.com/core-js/client/shim.min.js:7:26035\n" ​ __proto__: {…} ​​ constructor: function Error() ​​ message: "" ​​ name: "Error" ​​ stack: Getter & Setter ​​ toSource: function toSource() ​​ toString: function toString() ​​ __proto__: Object { … }

I get the following error after i submit a simulation class. Could you please advice ?

Exception in thread "main" java.lang.IllegalArgumentException: User defined Simulation class com.alh.store.gatling.simulation.BasicSimulation could not be loaded at io.gatling.app.Selection$Selector.findUserDefinedSimulationInClassloader$1(Selection.scala:80) at io.gatling.app.Selection$Selector.$anonfun$singleSimulationFromConfig$4(Selection.scala:85) at scala.Option.orElse(Option.scala:447) at io.gatling.app.Selection$Selector.$anonfun$singleSimulationFromConfig$3(Selection.scala:85) at scala.Option.flatMap(Option.scala:271) at io.gatling.app.Selection$Selector.singleSimulationFromConfig(Selection.scala:83) at io.gatling.app.Selection$Selector.$anonfun$selection$1(Selection.scala:52) at scala.Option.getOrElse(Option.scala:189) at io.gatling.app.Selection$Selector.selection(Selection.scala:44) at io.gatling.app.Selection$.apply(Selection.scala:36) at io.gatling.app.Runner.run0(Runner.scala:73) at io.gatling.app.Runner.run(Runner.scala:60) at io.gatling.app.Gatling$.start(Gatling.scala:80) at io.gatling.app.Gatling$.fromArgs(Gatling.scala:46) at io.gatling.app.Gatling$.main(Gatling.scala:38) at io.gatling.app.Gatling.main(Gatling.scala)Caused by: java.lang.ClassNotFoundException: com.alh.store.gatling.simulation.BasicSimulation at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at io.gatling.app.Selection$Selector.$anonfun$singleSimulationFromConfig$2(Selection.scala:71) at scala.util.Try$.apply(Try.scala:213) at io.gatling.app.Selection$Selector.findUserDefinedSimulationInClassloader$1(Selection.scala:71) ... 15 more[]