Uploaded image for project: 'JBoss OSGi'
  1. JBoss OSGi
  2. JBOSGI-792

Initial bundles fail to resolve if runtime name differs

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0
    • Component/s: None
    • Labels:
      None

      Description

      If you load a deployment with a different runtime name than the deployment name deployment will fail on server start.

      [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]         ],
      

      While this is in domain mode it also occurs in standalone mode

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                arcivanov Arcadiy Ivanov
                Reporter:
                sanderst Sander Stoel
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: