Luke, thanks for writing this test!! I looked at your test (esp. org.apache.solr.client.solrj.impl.Http2SolrClientTest#testIdleTimeoutWithHttpClient ) in more detail. You tested going from having a sufficient amount of idle timeout for the request to succeed, then down to a lower amount, asserting it failed. But we want the other way around -- low to high. I pushed this change to your PR and the test failed. Can you look please? Unless I'm missing something, this failure demonstrates the problem I am ringing the alarm bells about.
https://issues.apache.org/jira/browse/SOLR-13605 Ah, thanks for reminding me. That issue is about Apache based HTTP SolrClient, and yes, it seems like the "reverse" problem. On Thu, May 22, 2025 at 7:47 PM Chris Hostetter <hossman_luc...@fucit.org> wrote: > > > : Then I noticed something insidious: If an Http2SolrClient (Jetty) is > : created using the builder's withHttpClient(...) method, then the idle > (aka > : socket) timeout & connection timeout (and basically any other setting > : that's inside the Jetty HttpClient) cannot *actually* be customized > : henceforth. This should be pretty obvious, when you think about it > (duh). > > Deja Vu... > > https://issues.apache.org/jira/browse/SOLR-13605 > > ...except now we have the reverse problem? > > > > -Hoss > http://www.lucidworks.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org > For additional commands, e-mail: dev-h...@solr.apache.org > >
