Thanks, Trustin. I took a look at the thread pool stuff and think i was
just a little confused when i wrote up the question. I debugged the server
and found my threads were returning to the pool as they should. We are
seeing this exception a lot, but will now assume it is an issue w/ the
network
Hi Matt,
You can simply ignore 'Connection reset by peer' error. It's a little
bit different from normal close, it anyways means the connection has
been closed.
And ExecutorFilter doesn't do anything related with choosing a thread.
It just calls execute() method on the Executor you specified.
Also noticed during testing in my own dev environment that if I wait for a
few minutes between sending messages to the server, a new thread is always
used by the executor filter.
For example, if I connect and send three requests one after the other, the
executor filter uses thread-1 for each reque
