[KARAF-4100] [karaf-3.0.x] Error resolving artifact of feature due to org.ops4j.pax.url.mvn.cfg not loaded yet

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.5
• Fix Version/s: 4.1.0
• Component/s: karaf

Environment

Karaf 3.0.4, Windows 7

• Assignee: Grzegorz Grzybek
• Reporter: Jerry Meng
• Created: 06/Nov/15 18:08
• Updated: 19/Dec/19 17:29
• Resolved: 19/Dec/16 09:36

Description

I set the mvn repository to the karaf_home/system directory in org.ops4j.pax.url.mvn.cfg.

However, I found there is a chance that Karaf was trying to access the Internet and threw an exception since it's in a closed environment.

Error resolving artifact org.apache.karaf.features:enterprise:xml:features:3.0.4: Could not transfer artifact org.apache.karaf.features:enterprise:xml:features:3.0.4 from/to  (http://mvn.mycompany.net/content/groups/public): Not authorized , ReasonPhrase:Unauthorized.

Root Cause
=========

Through further tracking, the root cause may happen in org.ops4j.pax.url.mvn.internal.Activator (pax-url-aether). The pax url fails to load org.ops4j.pax.url.mvn.cfg before Karaf connects the feature url. Therefore Karaf ignores my settings in the configuration file but tries to access default remote repository. Here are some logs to describe the situation...

1. activator.updated.dictionary: null
2. updated directory from safeRegisterService: null
3. activator.openConnection: mvn:org.apache.karaf.features/enterprise/3.0.4/xml/features
4. Unable to add features repository mvn:org.apache.karaf.features/enterprise/3.0.4/xml/features at startup
5. updated directory from safeRegisterService: {felix.fileinstall.filename={file:/D:/karaf/etc/org.ops4j.pax.url.mvn.cfg... }
6. activator.updated.dictionary: {felix.fileinstall.filename={file:/D:/karaf/etc/org.ops4j.pax.url.mvn.cfg... }

Workaround
=========
I'm not sure if I should call this a bug, but in my case I can assume org.ops4j.pax.url.mvn.cfg is existent definitely.
Therefore, I make Activator.openConnection to wait if the Dictionary is not set.
Then invoke notifyAll in Activator.updated after receiving an non-null Dictionary.

Issue Links

• Is contained by: KARAF-4762 Upgrade to PaxUrl 2.5.1
• is duplicated by: KARAF-571 Karaf failed to startup due to maven resolution failure on specific cases.
• is duplicated by: KARAF-4719 Aether cannot to resolve m2 repositories after adjustments in org.ops4j.pax.url.mvn.cfg