java.lang.IllegalStateException: Invalid BundleContext.)

cxf-users | Tang Yong | 4 years ago
  1. 0

    Re: About DOSGI-152 status

    cxf-users | 4 years ago | Tang Yong
    java.lang.IllegalStateException: Invalid BundleContext.)
  2. 0

    Re: About DOSGI-152 status

    cxf-users | 4 years ago | Tang Yong
    java.lang.IllegalStateException: Invalid BundleContext.)
  3. 0

    Cytoscape does not start from terminal

    Google Groups | 1 month ago | Assa Yeroslaviz
    java.lang.RuntimeException: Couldn't find service: org.cytoscape.util.swing.IconManager
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    h3.Summary Enabling and installing JIRA Agile; or updating JIRA Agile in a certain way is causing it to fail. h3.Steps to Reproduce Install JIRA Agile in the specific order that makes it not work, which is still to be discovered. h3.Expected Results JIRA Agile enables successfully. h3.Actual Results The following stack trace is thrown: {code}2013-12-08 18:18:36,903 pool-15-thread-1 INFO hhunfeld 1095x47194x1 1p0no84 172.20.2.134 /rest/plugins/self-update/1.0/ [atlassian.plugin.util.WaitUntil] Plugins that have yet to be enabled: [com.pyxis.greenhopper.jira], 2 seconds remaining 2013-12-08 18:18:37,903 pool-15-thread-1 INFO hhunfeld 1095x47194x1 1p0no84 172.20.2.134 /rest/plugins/self-update/1.0/ [atlassian.plugin.util.WaitUntil] Plugins that have yet to be enabled: [com.pyxis.greenhopper.jira], 1 seconds remaining 2013-12-08 18:18:38,903 pool-15-thread-1 INFO hhunfeld 1095x47194x1 1p0no84 172.20.2.134 /rest/plugins/self-update/1.0/ [atlassian.plugin.util.WaitUntil] Plugins that have yet to be enabled: [com.pyxis.greenhopper.jira], 0 seconds remaining 2013-12-08 18:18:39,903 pool-15-thread-1 INFO hhunfeld 1095x47194x1 1p0no84 172.20.2.134 /rest/plugins/self-update/1.0/ [atlassian.plugin.manager.DefaultPluginManager] Disabling com.pyxis.greenhopper.jira 2013-12-08 18:18:40,872 pool-15-thread-1 ERROR hhunfeld 1095x47194x1 1p0no84 172.20.2.134 /rest/plugins/self-update/1.0/ [atlassian.plugin.manager.PluginEnabler] Unable to start the following plugins due to timeout while waiting for plugin to enable: com.pyxis.greenhopper.jira 2013-12-08 18:18:41,872 ThreadPoolAsyncTaskExecutor::Thread 39 ERROR hhunfeld 1095x47194x1 1p0no84 172.20.2.134 /rest/plugins/self-update/1.0/ [internal.dependencies.startup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.pyxis.greenhopper.jira], unsatisfied dependencies: none java.lang.IllegalStateException: Invalid BundleContext. at org.apache.felix.framework.BundleContextImpl.checkValidity(BundleContextImpl.java:365) at org.apache.felix.framework.BundleContextImpl.getServiceReferences(BundleContextImpl.java:307) at org.springframework.osgi.util.OsgiServiceReferenceUtils.getServiceReferences(OsgiServiceReferenceUtils.java:159) at org.springframework.osgi.util.OsgiServiceReferenceUtils.getServiceReferences(OsgiServiceReferenceUtils.java:195) at org.springframework.osgi.util.OsgiServiceReferenceUtils.isServicePresent(OsgiServiceReferenceUtils.java:327) at org.springframework.osgi.extender.internal.dependencies.startup.MandatoryServiceDependency.isServicePresent(MandatoryServiceDependency.java:82) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyServiceManager.doFindDependencies(DependencyServiceManager.java:287) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyServiceManager.access$700(DependencyServiceManager.java:40) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyServiceManager$1.run(DependencyServiceManager.java:213) at org.springframework.osgi.extender.internal.util.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:124) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyServiceManager.findServiceDependencies(DependencyServiceManager.java:209) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.stageOne(DependencyWaiterApplicationContextExecutor.java:239) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.refresh(DependencyWaiterApplicationContextExecutor.java:169) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.refresh(AbstractDelegatedExecutionApplicationContext.java:175) at org.springframework.osgi.extender.internal.activator.ContextLoaderListener$2.run(ContextLoaderListener.java:716) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 2013-12-08 18:18:41,872 ThreadPoolAsyncTaskExecutor::Thread 39 ERROR hhunfeld 1095x47194x1 1p0no84 172.20.2.134 /rest/plugins/self-update/1.0/ [extender.internal.activator.ContextLoaderListener] Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.pyxis.greenhopper.jira, config=osgibundle:/META-INF/spring/*.xml)) java.lang.IllegalStateException: Invalid BundleContext. at org.apache.felix.framework.BundleContextImpl.checkValidity(BundleContextImpl.java:365) at org.apache.felix.framework.BundleContextImpl.getServiceReferences(BundleContextImpl.java:307) at org.springframework.osgi.util.OsgiServiceReferenceUtils.getServiceReferences(OsgiServiceReferenceUtils.java:159) at org.springframework.osgi.util.OsgiServiceReferenceUtils.getServiceReferences(OsgiServiceReferenceUtils.java:195) at org.springframework.osgi.util.OsgiServiceReferenceUtils.isServicePresent(OsgiServiceReferenceUtils.java:327) at org.springframework.osgi.extender.internal.dependencies.startup.MandatoryServiceDependency.isServicePresent(MandatoryServiceDependency.java:82) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyServiceManager.doFindDependencies(DependencyServiceManager.java:287) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyServiceManager.access$700(DependencyServiceManager.java:40) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyServiceManager$1.run(DependencyServiceManager.java:213) at org.springframework.osgi.extender.internal.util.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:124) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyServiceManager.findServiceDependencies(DependencyServiceManager.java:209) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.stageOne(DependencyWaiterApplicationContextExecutor.java:239) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.refresh(DependencyWaiterApplicationContextExecutor.java:169) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.refresh(AbstractDelegatedExecutionApplicationContext.java:175) at org.springframework.osgi.extender.internal.activator.ContextLoaderListener$2.run(ContextLoaderListener.java:716) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source){code} Once JAG is disabled or stalled, all boards are disabled. h3.Workaround # Increase the plugin start timeout from default 60 seconds to 300 seconds by specifying the startup parameter *-Datlassian.plugins.enable.wait=300*. For a better description please see the Workaround on [JIRA System Plugin Timeout While Waiting for Plugins to Enable|https://confluence.atlassian.com/display/JIRAKB/JIRA+System+Plugin+Timeout+While+Waiting+for+Plugins+to+Enable]. Note that if you do not specify the increased timeout, you will likely run into the same problem when you try updating the plugin to a newer version in UPM. # Restart JIRA. This should enable back JIRA Agile # If JIRA Agile boards are missing, perform a re-index to bring back all the missing board. (!) So far Atlassian still unable to reproduce this behaviour explicitly, this bug ticket is created to keep track how many users are affected and find a common pattern to reproduce the bug.

    Atlassian JIRA | 3 years ago | Vicky Kharisma [Atlassian]
    java.lang.IllegalStateException: Invalid BundleContext.
  6. 0

    Karaf - User - Reasons that triggers IllegalStateException: Invalid BundleContext

    nabble.com | 3 months ago
    java.lang.IllegalStateException: Invalid BundleContext.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.IllegalStateException

      Invalid BundleContext.)

      at org.apache.felix.framework.Felix.setActiveStartLevel()
    2. Apache Felix Framework
      FrameworkStartLevelImpl.run
      1. org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1214)
      2. org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:295)
      2 frames
    3. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:722)
      1 frame