[
https://issues.apache.org/jira/browse/FLINK-16947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285028#comment-17285028
]
Lari Hotari edited comment on FLINK-16947 at 2/16/21, 4:38 AM:
---------------------------------------------------------------
I came across a similar issue in Apache Pulsar's build. The bug causing the
failures where the error message is "Could not transfer artifact
groupId:artifactId:1.2.3 from/to central ([https://repo1.maven.org/maven2]):
Entry [id:1280][route:\\{s}->https://repo1.maven.org:443][state:null] has not
been leased from this pool" is HTTPCORE-634 . It has been fixed in HttpCore
4.4.14 . This fix isn't in a released version of Maven or the Maven Wagon Http
library. I have created a PR [https://github.com/apache/maven-wagon/pull/76] to
get the changes first in Maven Wagon.
The immediate workaround is to replace the existing
MAVEN_HOME/lib/wagon-http-*-shaded.jar file with
[https://jitpack.io/com/github/lhotari/maven-wagon/wagon-http/5ff79d284/wagon-http-5ff79d284-shaded.jar]
(compiled version of maven-wagon PR 76). This seems to work at least in Maven
3.6.3 .
Simple bash script to replace the Maven built-in wagon-http version with the
patched one:
{code:java}
#!/bin/bash
MAVEN_HOME=$(mvn -v |grep 'Maven home:' | awk '{ print $3 }')
if [ -d "$MAVEN_HOME" ]; then
cd "$MAVEN_HOME/lib"
rm wagon-http-*-shaded.jar
curl -O
https://jitpack.io/com/github/lhotari/maven-wagon/wagon-http/5ff79d284/wagon-http-5ff79d284-shaded.jar
fi {code}
I also tried to use the build / extensions / extension element to override the
built-in wagon-http version, but in my quick experiment that didn't seem to
work.
I hope this helps!
was (Author: lhotari):
I came across a similar issue in Apache Pulsar's build. The bug causing the
failures where the error message is "Could not transfer artifact
groupId:artifactId:1.2.3 from/to central ([https://repo1.maven.org/maven2]):
Entry [id:1280][route:\{s}->https://repo1.maven.org:443][state:null] has not
been leased from this pool" is HTTPCORE-634 . It has been fixed in HttpCore
4.4.14 . This fix isn't in a released version of Maven or the Maven Wagon Http
library. I have created a PR [https://github.com/apache/maven-wagon/pull/76] to
get the changes first in Maven Wagon.
The immediate workaround is to replace the existing
MAVEN_HOME/lib/wagon-http-*-shaded.jar file with
[https://jitpack.io/com/github/lhotari/maven-wagon/wagon-http/5ff79d284/wagon-http-5ff79d284-shaded.jar]
(compiled version of maven-wagon PR 76). This seems to work at least in Maven
3.6.3 .
Simple bash script to replace the Maven built-in wagon-http version with the
patched one:
{code:java}
#!/bin/bash
MAVEN_HOME=$(mvn -v |grep 'Maven home:' | awk '{ print $3 }')
if [ -d "$MAVEN_HOME" ]; then
cd "$MAVEN_HOME/lib"
rm wagon-http-*-shaded.jar
curl -O
https://jitpack.io/com/github/lhotari/maven-wagon/wagon-http/5ff79d284/wagon-http-5ff79d284-shaded.jar
fi {code}
I also tried to use the build / extensions / extension tag to override the
built-in wagon-http version, but in my quick experiment that didn't seem to
work.
I hope this helps!
> ArtifactResolutionException: Could not transfer artifact. Entry [...] has
> not been leased from this pool
> ---------------------------------------------------------------------------------------------------------
>
> Key: FLINK-16947
> URL: https://issues.apache.org/jira/browse/FLINK-16947
> Project: Flink
> Issue Type: Bug
> Components: Build System / Azure Pipelines
> Reporter: Piotr Nowojski
> Priority: Critical
> Labels: test-stability
>
> https://dev.azure.com/rmetzger/Flink/_build/results?buildId=6982&view=logs&j=c88eea3b-64a0-564d-0031-9fdcd7b8abee&t=1e2bbe5b-4657-50be-1f07-d84bfce5b1f5
> Build of flink-metrics-availability-test failed with:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.22.1:test (end-to-end-tests)
> on project flink-metrics-availability-test: Unable to generate classpath:
> org.apache.maven.artifact.resolver.ArtifactResolutionException: Could not
> transfer artifact org.apache.maven.surefire:surefire-grouper:jar:2.22.1
> from/to google-maven-central
> (https://maven-central-eu.storage-download.googleapis.com/maven2/): Entry
> [id:13][route:{s}->https://maven-central-eu.storage-download.googleapis.com:443][state:null]
> has not been leased from this pool
> [ERROR] org.apache.maven.surefire:surefire-grouper:jar:2.22.1
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] google-maven-central
> (https://maven-central-eu.storage-download.googleapis.com/maven2/,
> releases=true, snapshots=false),
> [ERROR] apache.snapshots (https://repository.apache.org/snapshots,
> releases=false, snapshots=true)
> [ERROR] Path to dependency:
> [ERROR] 1) dummy:dummy:jar:1.0
> [ERROR] 2) org.apache.maven.surefire:surefire-junit47:jar:2.22.1
> [ERROR] 3) org.apache.maven.surefire:common-junit48:jar:2.22.1
> [ERROR] 4) org.apache.maven.surefire:surefire-grouper:jar:2.22.1
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :flink-metrics-availability-test
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
