-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: JBoss A-MQ 6.2.1
-
Fix Version/s: JBoss A-MQ 6.3
-
Component/s: None
-
Labels:None
-
Environment:
JBoss A-MQ 6.2.1 R2 (earlier versions might also be affected)
-
Steps to Reproduce:
-
Sprint:Sprint 6 - towards CR1
In an environment with no access, A-MQ 6.2.1 R2 won't start cleanly, because it tries to read from repo1.maven.org:
2016-06-17 11:33:18,166 | WARN | pool-3-thread-1 | AetherBasedResolver | mvn.internal.AetherBasedResolver 659 | 5 - org.ops4j.pax.logging.pax-logging-api - 1.8.4 | Error resolving artifactorg.apache.geronimo.specs:geronimo-osgi-registry:jar:1.1:Could not transfer artifact org.apache.geronimo.specs:geronimo-osgi-registry:jar:1.1 from/to maven.central.repo (http://repo1.maven.org/maven2/): Connect to repo1.maven.org:80 [repo1.maven.org/127.0.0.1] failed: Connection refused
|
shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not transfer artifact org.apache.geronimo.specs:geronimo-osgi-registry:jar:1.1 from/to maven.central.repo (http://repo1.maven.org/maven2/): Connect to repo1.maven.org:80 [repo1.maven.org/127.0.0.1] failed: Connection refused
|
at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)[4:org.ops4j.pax.url.mvn:2.4.7]
|
at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)[4:org.ops4j.pax.url.mvn:2.4.7]
|
at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)[4:org.ops4j.pax.url.mvn:2.4.7]
|
at shaded.org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294)[4:org.ops4j.pax.url.mvn:2.4.7]
|
Depending on how long it takes Internet operations to fail in the target environment A-MQ may, or may not, eventually start. If it does start, the long-term consequences are unclear.
