Author zyasoft
Recipients amak, jeff.allen, zyasoft
Date 2016-09-02.20:24:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The relevant Netty change is, which happened in 4.0.16; but most likely 4.1 made this more prominent. My recollection is that I don't believe it's possible to have Python socket closing semantics without attempting to close the pool as soon as possible - as it is, we wait up to 100ms. See the _realsocket._finish_closing method in Lib/ for more on what is being done to close the socket.

Therefore we need to take advantage of the rejected logger, which is under the name io.netty.util.concurrent.DefaultPromise.rejectedExecution; see

Assuming SL4J + Logback is still being used, this advice on StackOverflow should be relevant: In particular we can put a suitably configured logback.xml in jython.jar or jython-dev.jar to remove this logging:
Date User Action Args
2016-09-02 20:24:47zyasoftsetmessageid: <>
2016-09-02 20:24:47zyasoftsetrecipients: + zyasoft, amak, jeff.allen
2016-09-02 20:24:47zyasoftlinkissue2517 messages
2016-09-02 20:24:46zyasoftcreate