-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not transfer artifact io.zipkin.brave:brave-bom:pom:5.13.9 #9192
Comments
@sschuberth
but still the same behavior 20:53:37.322 [DefaultDispatcher-worker-1] DEBUG org.ossreviewtoolkit.plugins.packagemanagers.maven.utils.MavenSupport$requestRemoteArtifact$4$2 - Transfer failed for repository with ID 'central': GET_EXISTENCE FAILED https://repo-xxxxx.xxxxx.xxx/repository/maven-public/com/google/cloud/spring-cloud-gcp-starter-pubsub/3.5.5/spring-cloud-gcp-starter-pubsub-3.5.5-sources.jar <> /home/ort/.m2/repository/com/google/cloud/spring-cloud-gcp-starter-pubsub/3.5.5/spring-cloud-gcp-starter-pubsub-3.5.5-sources.jar
20:53:37.323 [DefaultDispatcher-worker-1] DEBUG org.ossreviewtoolkit.plugins.packagemanagers.maven.utils.MavenSupport - ArtifactNotFoundException: Could not find artifact com.google.cloud:spring-cloud-gcp-starter-pubsub:jar:sources:3.5.5 in central (https://repo-xxxxx.xxxxx.xxx/repository/maven-public/)
20:53:37.323 [DefaultDispatcher-worker-1] DEBUG org.ossreviewtoolkit.plugins.packagemanagers.maven.utils.MavenSupport - Trying to download artifact 'com.google.cloud:spring-cloud-gcp-starter-pubsub:jar:sources:3.5.5' from https://repo.maven.apache.org/maven2/com/google/cloud/spring-cloud-gcp-starter-pubsub/3.5.5/spring-cloud-gcp-starter-pubsub-3.5.5-sources.jar.
20:53:37.323 [DefaultDispatcher-worker-1] DEBUG org.eclipse.aether.internal.impl.DefaultTransporterProvider - Using transporter HttpTransporter with priority 5.0 for https://repo.maven.apache.org/maven2
20:53:37.323 [DefaultDispatcher-worker-1] DEBUG org.eclipse.aether.internal.impl.DefaultRepositoryConnectorProvider - Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2
20:53:37.324 [DefaultDispatcher-worker-1] DEBUG org.apache.http.client.protocol.RequestAddCookies - CookieSpec selected: standard
20:53:37.324 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.conn.PoolingHttpClientConnectionManager - Connection request: [route: {s}->https://repo.maven.apache.org:443][total available: 1; route allocated: 0 of 50; total allocated: 1 of 100]
20:53:37.324 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.conn.PoolingHttpClientConnectionManager - Connection leased: [id: 15][route: {s}->https://repo.maven.apache.org:443][total available: 1; route allocated: 1 of 50; total allocated: 2 of 100]
20:53:37.324 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.execchain.MainClientExec - Opening connection {s}->https://repo.maven.apache.org:443
20:53:37.349 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.conn.DefaultHttpClientConnectionOperator - Connecting to repo.maven.apache.org/199.232.16.215:443
20:53:37.349 [DefaultDispatcher-worker-1] DEBUG org.apache.http.conn.ssl.SSLConnectionSocketFactory - Connecting socket to repo.maven.apache.org/199.232.16.215:443 with timeout 10000
20:53:47.360 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.conn.DefaultManagedHttpClientConnection - http-outgoing-15: Shutdown connection
20:53:47.360 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.execchain.MainClientExec - Connection discarded
20:53:47.360 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.conn.PoolingHttpClientConnectionManager - Connection released: [id: 15][route: {s}->https://repo.maven.apache.org:443][total available: 1; route allocated: 0 of 50; total allocated: 1 of 100]
20:53:47.361 [DefaultDispatcher-worker-1] DEBUG org.ossreviewtoolkit.plugins.packagemanagers.maven.utils.MavenSupport$requestRemoteArtifact$4$2 - Transfer failed for repository with ID 'central': GET_EXISTENCE FAILED https://repo.maven.apache.org/maven2/com/google/cloud/spring-cloud-gcp-starter-pubsub/3.5.5/spring-cloud-gcp-starter-pubsub-3.5.5-sources.jar <> /home/ort/.m2/repository/com/google/cloud/spring-cloud-gcp-starter-pubsub/3.5.5/spring-cloud-gcp-starter-pubsub-3.5.5-sources.jar
20:53:47.363 [DefaultDispatcher-worker-1] DEBUG org.ossreviewtoolkit.plugins.packagemanagers.maven.utils.MavenSupport - ArtifactTransferException: Could not transfer artifact com.google.cloud:spring-cloud-gcp-starter-pubsub:jar:sources:3.5.5 from/to central (https://repo.maven.apache.org/maven2): Connect to repo.maven.apache.org:443 [repo.maven.apache.org/199.232.16.215] failed: Connect timed out
Caused by: ConnectTimeoutException: Connect to repo.maven.apache.org:443 [repo.maven.apache.org/199.232.16.215] failed: Connect timed out
Caused by: SocketTimeoutException: Connect timed out In the code in file: plugins/package-managers/maven/src/main/kotlin/utils/MavenSupport.kt there is public maven Central repository hardcoded. The settings.xml file that I use points to use only corporate internal repo and still ORT reaches for external repository. *Beside the artifact |
As you can see from its green (instead of purple) state, the PR is not merged yet, so it's not included in any image. You would need to build the PR from source to test it currently. |
Not sure whether #9263 will have an impact here, since it addresses a very specific situation. The problems described here seem to be rather general when using ORT behind a proxy. We have a proxy in our setup as well. To make it work, we pass the proxy-related system properties to the Java VM running ORT as described here. Especially the |
Describe the bug
I found an issue with ORT Analyzer.
I use ORT in corporate network. No connection to Internet.
The project is simple maven project with just one dependency:
In order to point the maven repository I created ~/.m2/settings.xml file.
I tried both ways:
Setting mirror as mirrorOf central and setting mirror as active profile
Both are pointing in the end to the same issue
Despite the fact that I overwritten central repository by the corporate mirror ORT has hardcoded address to the mavenCentral repo
What is interesting is the fact that the package
io.zipkin.brave:brave-bom:pom:5.13.9
exists in my mirror so there is no reason to go to mvnCentralSo there are to cases:
ORT cannot find the artifact while it exists in the mirror. (maybe to short time out to get the pom)
How to overide mavenCentral repository so in case there is no Internet connection the process will not waste time for timeouts
ORT works ok when the access to Internet is granted.
PS: I cannot use slack for communication
The text was updated successfully, but these errors were encountered: