Sounds like its Jetty's selector bug triggering again, but for SSL
instead of plain text HTTP.
> We recently (few days ago) upgraded to the latest RC (2.1.7-rc0). I think we
> haven't seen this issue before the upgrade but can't confirm 100%.
> And, I just upgraded java to 1.6.0_25 but this didn't help.
We did upgrade Jetty. Its possible there is a new Jetty bug.
> Is there a way to get more info logged for these warnings (full stack trace,
> IP Address of the incoming request, etc...)?
You would need to hand-edit the log4j.properties file in the Gerrit
WAR file (which is probably itself buried within a JAR file somewhere,
I forget where). We don't support changing the logging except by
editing the source and rebuilding.
Yes. I'll revert that upgrade. We will use the same Jetty we have in 2.1.6.1.