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
Graphite: NPE on shutdown #3352
Comments
Have a look at the stacktrace: this crash happens in the Graphite DataWriter when Gatling shuts down. It has nothing to do with HTTP nor WebSockets. I suspect you use something like maxDuration that forcefully closes Gatling, and can cause some race conditions on shut down. The HTML reports are still being generated, so this is more an inconvenience than a critical issue and I don't think me or the other Gatling Corp people will invest time on this. Then, we'd love a contribution! |
I suspect one should just try to catch the exception in the TcpSender and ignore it. Gatling is being shutdown and there's nothing to do to try to recover. |
Yes I have the graphite connection enabled, (however influxDB is not started). Thank you for your hint, I'll see if I can find time to try and create a pull request. |
Closing due to lack of activity. Moreover, such issue wasn't reported since then, so it's possible it was fixed in Akka (who knows). |
Not fixed yet, its so confusing, as the test runs ok, but there is an error `Simulation XXXXXXXXX completed in 1 seconds Parsing log file(s)... ` |
I'm now experiencing this issue as well.
Setup:
Win 8.1
Gatling 2.2.5
Async websockets checks are used, together with http
Test target is on the same machine
As you can see in the screenshot below this happens after the simulation is completed.
The last thing the test does is
It does not reproduce every time though, but pretty often.
I managed to put a breakpoint on the line that throws this error, I don't know the issue though.
Below is a screenshot with variable values, let me know if there is anything I can try, I will upgrade my gatling version soon but as I see the changelog this is not fixed
This is a duplicate of #3052 but it is closed and it seems no one is looking at it :)
The text was updated successfully, but these errors were encountered: