Ryan Moquin created KARAF-2099:
----------------------------------
Summary: CLONE - Some bundles of cellar failed to startup from
time to time
Key: KARAF-2099
URL: https://issues.apache.org/jira/browse/KARAF-2099
Project: Karaf
Issue Type: Bug
Components: cellar-core
Affects Versions: cellar-2.2.3
Environment: Linux, Ubuntu 11.10.
Reporter: Ryan Moquin
Assignee: Jean-Baptiste Onofré
Fix For: cellar-3.0.0, cellar-2.2.4
>From time to time (without concrete steps to reproduce) some of cellar bundles
>states in "GracePeriod" blueprint status and after long period change own
>blueprint status into "failed".
Log contains such exceptions:
19:28:49,302 | ERROR | rint Extender: 2 | ntainer.BlueprintContainerImpl$1 293
| 10 - org.apache.aries.blueprint - 0.3.1 | Unable to start blueprint container
for bundle org.apache.karaf.cellar.fe
atures due to unresolved dependencies
[(objectClass=org.apache.karaf.cellar.core.GroupManager)]
java.util.concurrent.TimeoutException
at
org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:287)[10:org.apache.aries.blueprint:0.3.1]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)[:1.6.0_30]
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)[:1.6.0_30]
at java.util.concurrent.FutureTask.run(FutureTask.java:138)[:1.6.0_30]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)[:1.6.0_30]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)[:1.6.0_30]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)[:1.6.0_30]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)[:1.6.0_30]
at java.lang.Thread.run(Thread.java:662)[:1.6.0_30]
19:28:49,311 | ERROR | rint Extender: 2 | ntainer.BlueprintContainerImpl$1 293
| 10 - org.apache.aries.blueprint - 0.3.1 | Unable to start blueprint container
for bundle org.apache.karaf.cellar.bundle due to unresolved dependencies
[(objectClass=org.apache.karaf.cellar.core.GroupManager)]
java.util.concurrent.TimeoutException
at
org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:287)[10:org.apache.aries.blueprint:0.3.1]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)[:1.6.0_30]
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)[:1.6.0_30]
at java.util.concurrent.FutureTask.run(FutureTask.java:138)[:1.6.0_30]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)[:1.6.0_30]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)[:1.6.0_30]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)[:1.6.0_30]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)[:1.6.0_30]
at java.lang.Thread.run(Thread.java:662)[:1.6.0_30]
19:28:49,366 | ERROR | rint Extender: 2 | ntainer.BlueprintContainerImpl$1 293
| 10 - org.apache.aries.blueprint - 0.3.1 | Unable to start blueprint container
for bundle org.apache.karaf.cellar.dosgi due to unresolved dependencies
[(objectClass=org.apache.karaf.cellar.core.event.EventTransportFactory)]
java.util.concurrent.TimeoutException
at
org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:287)[10:org.apache.aries.blueprint:0.3.1]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)[:1.6.0_30]
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)[:1.6.0_30]
at java.util.concurrent.FutureTask.run(FutureTask.java:138)[:1.6.0_30]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)[:1.6.0_30]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)[:1.6.0_30]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)[:1.6.0_30]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)[:1.6.0_30]
at java.lang.Thread.run(Thread.java:662)[:1.6.0_30]
19:28:49,547 | ERROR | rint Extender: 2 | ntainer.BlueprintContainerImpl$1 293
| 10 - org.apache.aries.blueprint - 0.3.1 | Unable to start blueprint container
for bundle org.apache.karaf.cellar.management due to unresolved dependencies
[(objectClass=org.apache.karaf.cellar.core.command.ExecutionContext)]
java.util.concurrent.TimeoutException
at
org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:287)[10:org.apache.aries.blueprint:0.3.1]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)[:1.6.0_30]
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)[:1.6.0_30]
at java.util.concurrent.FutureTask.run(FutureTask.java:138)[:1.6.0_30]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)[:1.6.0_30]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)[:1.6.0_30]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)[:1.6.0_30]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)[:1.6.0_30]
at java.lang.Thread.run(Thread.java:662)[:1.6.0_30]
For example, I got this situation after such execution:
1) run two karafs.
2) install cellar on node1.
3) stop node1, update hazelcast config to "multicast=disabled"
4) install cellar on node2
5) start node1.
6) check -- nodes do not see each other.
7) stop both nodes.
8) revert changes in cellar on node1 (enable multicast)
9) start both nodes -- here cellar bundles (config, features, bundle, dosgi,
management) on node2 hangs in mentioned status.
Restart of node helped, but after some time (with similar steps) it hangs
again. Only restart helped again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
