Kundan Atre
Reputation: 3961
java.io.IOException: Remotely closed in gatling
I have recorded scala script using gatling recorder; but when I run it, it starts showing java.io.IOException: Remotely closed error
Is there any workaround for this?
Upvotes: 1
Views: 3388
Answers (1)
Stephane Landelle
Reputation: 7038
That's probably not a Gatling issue, but a real error with your server forcefully closing the connection while Gatling is writing on it.
It could be that your server cannot withstand the load and aggressively closes random connections, or some misconfiguration in some network component.
Upvotes: 1
Related Questions
- Gatling feeder/parameter issue - Exception in thread "main" java.lang.UnsupportedOperationException
- Getting j.i.IOException: Premature close in Gatling
- Getting java.lang.ClassNotFoundException Gatling - when running Gatling
- Can't run Gatling simulation - error NoSuchElementException [gatling.scala:83]
- Unable to run the gatling test (jvm issue)
- Gatling request is not getting executed
- Gatling. ConnectException: connection timed out:
- Gatling throws InvalidActorNameException when testing long-poll HTTP requests
- Gatling check for java.io.IOException: Remotely closed
- java.util.concurrent.TimeoutException: Request timed out to in gatling