[
https://issues.apache.org/jira/browse/KARAF-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959451#comment-13959451
]
ASF GitHub Bot commented on KARAF-2882:
---------------------------------------
GitHub user entropydown opened a pull request:
https://github.com/apache/karaf/pull/34
don't wait for services for default url handler protocols
https://issues.apache.org/jira/browse/KARAF-2882
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/entropydown/karaf karaf-3.0.x
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/karaf/pull/34.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #34
----
commit cfa88a01d09ab226704d5f7842fca28f8530fc05
Author: Phillip Balli <pba...@cisco.com>
Date: 2014-04-03T22:24:14Z
don't wait for services for default url handler protocols
----
> using OBR resolver in feature files causes timeout to be hit
> ------------------------------------------------------------
>
> Key: KARAF-2882
> URL: https://issues.apache.org/jira/browse/KARAF-2882
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
> Affects Versions: 3.0.0
> Reporter: Phillip Balli
>
> When the features service installs a bundle resolved via OBR whose source is
> an "http" url (like when pointing to a karaf-cave server), it
> (karaf.features.internal.BundleManager) will wait for a service with the
> property url.handler.protocol=http to become available. Because there is no
> such service, a 30s timeout will hit for every obr-sourced bundle.
>
> I believe this is because url handlers for http, https, etc. are provided by
> default by felix. I'm not sure if these handlers were intended to be
> discoverable via properties in karaf.
> I have made a change to waitForUrlHandler to not wait for "default" protocols.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
