Closed rattboi closed 7 years ago
Yes. The error often occurs. I think it's because the client can't receive a exit status from a server process like timing issue or something.
Can't you execute new requests via groovyclient from another console, though the errors occur? I could reproduce the errors with your test script perhaps. But I can execute new request from another console while the test script is running. Even after stop the script emitting many error logs, I can execute new request, too.
If requires, reopen and add a comment.
We are attempting to use groovyserv to run a handful of healthchecks that are kicked off fairly regularly. Over time, groovyserver stops responding and must be bounced. Apparently there is some sort of leak.
I've created a small test script to demonstrate:
I manually started groovyserver with -v to get more verbose logging.
Below are the exceptions we are seeing:
We see these repeatedly, and over time, groovyserv becomes unresponsive and no longer executes new requests via groovyclient.