[GitHub] [maven-resolver] mvitz commented on pull request #274: [MRESOLVER-347] Ability to control conn reuse

["mvitz (via GitHub)" <gi...@apache.org>]

mvitz commented on PR #274:
URL: https://github.com/apache/maven-resolver/pull/274#issuecomment-1485185661

   @michael-o I started the discussion on the mailing list and asked if it's feasible to add some kind of configuration to resolve the problem of failing builds because the pool connection TTL is higher than the Azure limit.
   
   From my perspective, there are four possible ways to solve it.
   1. The user can deactivate the pooling altogether.
   2. The user can specify the TTL.
   3. The default TTL is set lower than Azure.
   4. The HttpClient can detect this kind of stale connection.
   
   Point 3. would, of course, be good because the next one will not run into the problem altogether, but even then, it may be useful to be able to configure this if in a specific environment the TTL can't be longer than e.g. two minutes.
   
   Therefore for me point 2. would be a good enough solution maybe combined with a more sensible default (= 3.) on top.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org