You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jesse WHite (JIRA)" <ji...@apache.org> on 2019/08/08 17:45:00 UTC
[jira] [Commented] (KARAF-6360) Intermittent "unknown protocol:
blueprint" errors on startup
[ https://issues.apache.org/jira/browse/KARAF-6360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903183#comment-16903183 ]
Jesse WHite commented on KARAF-6360:
------------------------------------
We're still getting bit by this pretty often in our CI tests. The attached logs show that the blueprint bundles don't actually start until after the features in [stage 2|http://karaf.922171.n3.nabble.com/Karaf-4-2-0-fails-when-installing-a-feature-with-a-configfile-tag-td4053615.html#a4053620] are installed.
Anything we can tune?
> Intermittent "unknown protocol: blueprint" errors on startup
> ------------------------------------------------------------
>
> Key: KARAF-6360
> URL: https://issues.apache.org/jira/browse/KARAF-6360
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Affects Versions: 4.2.6
> Reporter: Jesse WHite
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Attachments: karaf.blueprint.error.log
>
>
> We have some features that use Blueprint which are included in the
> featuresBoot and we've been noticing that these fail to load
> intermittently on startup.
> When it fails, we get a 'java.lang.IllegalStateException: Unknown
> protocol: blueprint' when our 'scv' feature. See attached log.
> The featuresBoot is defined as follows: https://github.com/OpenNMS/opennms/blob/bec4abd8e1e75d5a2e23d6b02fc7d93c0414902c/container/shared/src/main/filtered-resources/etc/org.apache.karaf.features.cfg#L34
> Given that the "aries-blueprint" feature is installed *before* the "scv" feature, I would expect the "blueprint" protocol to be known, but there appears to be some race condition here.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)