Hi Tamas, it occurs with 3.9.0 and 3.9.1. I hoped that the retry fix in 3.9.1 would solve the problem, but unfortunately it didn't.
Regards, Michael Am Fr., 24. März 2023 um 15:11 Uhr schrieb Tamás Cservenák < ta...@cservenak.net>: > Howdy, > > you did not specify which version exactly are you referring to? > As 3.9.x now have: > - 3.9.0 > - 3.9.1 > > And the latter is recommended to be used, especially in the Azure > environment. > > HTH > Tamas > > On Fri, Mar 24, 2023, 14:19 Michael Vitz > <vitz.mich...@googlemail.com.invalid> wrote: > > > Hi all, > > > > We recently switched from Maven 3.8.x to 3.9.x and all of a sudden, we > ran > > into connection timeouts during downloading the maven-jar-plugin after > all > > tests passed. > > > > After some digging, I suspect that it is a combination of GitHub Actions > > running on Azure which silently drops open connections after around four > > minutes (see discussion in > > https://github.com/actions/runner-images/issues/1499) and the switch to > > the > > native HTTP transport in Maven 3.9.x. > > Our tests take quite some time and because the maven-jar-plugin is > freshly > > downloaded after these, the used connection was opened before the tests > > were started and is dropped by Azure meanwhile. > > > > Our current workaround is switching to the old Wagon HTTP provider (with > > -Dmaven.resolver.transport=wagon) and setting a TTL for the used HTTP > pool > > (-Dmaven.wagon.httpconnectionManager.ttlSeconds=180) or disabling the > pool > > and keep alive (-Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false). > > > > Unfortunately, the new HTTP transport does not allow changing the TTL > > (which by default is -1 which means forever) or disabling it altogether. > It > > would be nice if such settings would be added in one of the next > releases. > > > > I would be happy to help/try to provide a patch on my own if this helps. > > > > Regards, > > Michael > > >
