amx.bpm.app in "waiting for dependencies" state due to unresolved OSGi bundles.
Article ID: KB0088147
Updated On:
| Products | Versions |
|---|---|
| TIBCO BPM Enterprise (formerly TIBCO ActiveMatrix BPM) | - |
| Not Applicable | - |
Description
Description:
amx.bpm.app in "waiting for dependencies" state after applying a hotfix. A restart of the BPMNodes does not resolve this issue.
"implementation.dac" component will show in START_FAILED or WAITING_FOR_DEPENDENCIES stated in output from: OSGi console or tibcohost describeApplications -includeComponents -nodeName BPMNode
Example:
Symptoms:
The application amx.bpm.app stays in a state waiting for dependencies, even if the node is restarted. The following log will be seen which indicates a number of unresolved osgi bundles. Component versions mentioned in the BPM.log will vary with BPM product versions, e.g. WorkManager implementation de/dac are 1.7.0.001 in BPM 3.1, 1.3.0.001 in BPM 1.3.0.
06 Jun 2012 11:42:24,788 [Start Level Event Dispatcher] [INFO ] stdout - amx.bpm.app_WorkManager_implementation.de_1.3.0.001
06 Jun 2012 11:42:24,790 [Start Level Event Dispatcher] [INFO ] stdout - org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: com.tibco.n2.de.auth; version="[1.2.0,2.0.0)"
06 Jun 2012 11:42:24,841 [Start Level Event Dispatcher] [INFO ] stdout - amx.bpm.app_WorkManager_implementation.dac_1.3.0.001
06 Jun 2012 11:42:24,842 [Start Level Event Dispatcher] [INFO ] stdout - org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: com.tibco.n2.dac.calendar; version="[1.2.0,2.0.0)"
06 Jun 2012 11:42:25,184 [Start Level Event Dispatcher] [INFO ] stdout - com.tibco.n2.dac.core
6 Jun 2012 11:42:25,185 [Start Level Event Dispatcher] [INFO ] stdout - org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Package uses conflict: Import-Package: org.springframework.cache.ehcache; version="[2.5.6,3.0.0)"
06 Jun 2012 11:42:25,199 [Start Level Event Dispatcher] [INFO ] stdout - com.tibco.n2.de.core
06 Jun 2012 11:42:25,200 [Start Level Event Dispatcher] [INFO ] stdout - org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Package uses conflict: Import-Package: org.springframework.cache.ehcache; version="[2.5.6,3.0.0)"
Cause:
Wiring of some components to bundles has failed to be resolved.
amx.bpm.app in "waiting for dependencies" state after applying a hotfix. A restart of the BPMNodes does not resolve this issue.
"implementation.dac" component will show in START_FAILED or WAITING_FOR_DEPENDENCIES stated in output from: OSGi console or tibcohost describeApplications -includeComponents -nodeName BPMNode
Example:
Exceptional state causes:
Waiting for dependency: componentURI=urn:amx:BPMEnvironment/amx.bpm.app/WorkManager/implementation.dac_1.7.0.001 state=NOT_RUNNING
Symptoms:
The application amx.bpm.app stays in a state waiting for dependencies, even if the node is restarted. The following log will be seen which indicates a number of unresolved osgi bundles. Component versions mentioned in the BPM.log will vary with BPM product versions, e.g. WorkManager implementation de/dac are 1.7.0.001 in BPM 3.1, 1.3.0.001 in BPM 1.3.0.
06 Jun 2012 11:42:24,790 [Start Level Event Dispatcher] [INFO ] stdout - org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: com.tibco.n2.de.auth; version="[1.2.0,2.0.0)"
06 Jun 2012 11:42:24,841 [Start Level Event Dispatcher] [INFO ] stdout - amx.bpm.app_WorkManager_implementation.dac_1.3.0.001
06 Jun 2012 11:42:24,842 [Start Level Event Dispatcher] [INFO ] stdout - org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: com.tibco.n2.dac.calendar; version="[1.2.0,2.0.0)"
06 Jun 2012 11:42:25,184 [Start Level Event Dispatcher] [INFO ] stdout - com.tibco.n2.dac.core
6 Jun 2012 11:42:25,185 [Start Level Event Dispatcher] [INFO ] stdout - org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Package uses conflict: Import-Package: org.springframework.cache.ehcache; version="[2.5.6,3.0.0)"
06 Jun 2012 11:42:25,199 [Start Level Event Dispatcher] [INFO ] stdout - com.tibco.n2.de.core
06 Jun 2012 11:42:25,200 [Start Level Event Dispatcher] [INFO ] stdout - org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Package uses conflict: Import-Package: org.springframework.cache.ehcache; version="[2.5.6,3.0.0)"
Cause:
Wiring of some components to bundles has failed to be resolved.
Issue/Introduction
amx.bpm.app in "waiting for dependencies" state due to unresolved OSGi bundles.
Resolution
Restart the affected node(s) in Resolve mode after seeing this issue.
1). Go to Infrastructure-->Nodes .
2). Make sure the BPMEnvironment is selected.
3). Select the BPMNode.
This refreshes the wiring of components to bundles (JARs). Note that this action involves a Node restart which will cause a temporary interruption to any applications running on the node.
Feedback
Yes
No
Powered by
