[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs
Sander Stoel (JIRA)
issues at jboss.org
Thu Apr 21 10:14:00 EDT 2016
[ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sander Stoel updated JBOSGI-792:
--------------------------------
Attachment: server.log
pom.xml
A test pom.xml and the resulting server.log
This is triggered by following the steps to reproduce.
I have not been able to create an automated test unfortunately
> Initial bundles fail to resolve if runtime name differs
> -------------------------------------------------------
>
> Key: JBOSGI-792
> URL: https://issues.jboss.org/browse/JBOSGI-792
> Project: JBoss OSGi
> Issue Type: Bug
> Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0
> Reporter: Sander Stoel
> Assignee: Arcadiy Ivanov
> Attachments: pom.xml, server.log
>
>
> If you load a deployment with a different runtime name than the deployment name deployment will fail on server start.
> {code}
> [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]",
> [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]"
> [Server:server] ],
> [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> [Server:server] "Services that were unable to start:" => [
> [Server:server] "jbosgi.SystemBundle",
> [Server:server] "jbosgi.SystemContext",
> [Server:server] "jbosgi.framework.ACTIVE",
> [Server:server] "jbosgi.framework.INIT",
> [Server:server] "jbosgi.internal.framework.ACTIVE"
> [Server:server] ],
> {code}
> While this is in domain mode it also occurs in standalone mode
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-osgi-issues
mailing list