[
https://issues.apache.org/jira/browse/KARAF-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek resolved KARAF-1674.
-------------------------------------
Resolution: Fixed
Fix Version/s: 4.0.8
4.1.0
> Abnormal Timeout with multiple maven repositories in pax-url
> ------------------------------------------------------------
>
> Key: KARAF-1674
> URL: https://issues.apache.org/jira/browse/KARAF-1674
> Project: Karaf
> Issue Type: Bug
> Affects Versions: 2.2.8
> Environment: karaf 2.2.8 with equinox running on debian with java
> 1.7.0_03
> Reporter: Sammy Ramareddy
> Assignee: Grzegorz Grzybek
> Fix For: 4.1.0, 4.0.8
>
>
> I'm having a strange issue where karaf needs a lot of time (around
> 5-10minutes) to generate for the first time the "features" tab in the
> webconsole or give some feedback to a "features:list" command in the ssh
> console.
> I currently have the following urls configured in
> $KARAF_HOME/etc/org.ops4j.pax.url.mvn.cfg:
> org.ops4j.pax.url.mvn.repositories= \
> http://192.168.2.224:8080/artifactory/repo@snapshots, \
> http://i0019231.subdomain.domain.tld:8080/artifactory/repo@snapshots
> The second url is actually pointing to the same artifactory repository as the
> first one, just running with another IP (within our VPN subnet).
> Once in production, karaf will run outside our network and will need to reach
> our artifactory server through a VPN connection, hence the need for two urls.
> The problem is the following: when the VPN connection is *not* running, and
> thus "i0019231.subdomain.domain.tld" is not reachable (its IP is 172.21.x.x),
> karaf needs 5-10 minutes to be able to start the features-plugin.
> When this is happening, the following entry is in the Karaf log:
> "failed to open bundleresource://78.fwk10937487/"
> where bundle 78 is org.apache.karaf.webconsole.features
> This issue happens only when the VPN client is not running and thus the
> second repository is not reachable. When the second url is reachable, then
> everything runs fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
