1 Reply Latest reply on Jan 27, 2011 5:49 AM by Claus Ibsen

    bundle did not finish in 10000ms

    a b Newbie

      Hi,

       

      for reasons, which I don't fully understand I keep getting this error:

       

      14:10:07,444 | ERROR |  Bundle Shutdown | RunnableTimedExecution           | oncurrent.RunnableTimedExecution  109 | Closing runnable for context OsgiBundleXmlApplicationContext(bundle=activemq-broker.xml, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs

      14:10:17,447 | ERROR |  Bundle Shutdown | RunnableTimedExecution           | oncurrent.RunnableTimedExecution  109 | Closing runnable for context OsgiBundleXmlApplicationContext(bundle=org.apache.cxf.bundle, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs

      14:10:27,450 | ERROR |  Bundle Shutdown | RunnableTimedExecution           | oncurrent.RunnableTimedExecution  109 | Closing runnable for context OsgiBundleXmlApplicationContext(bundle=servicemix-common, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs

      14:10:37,453 | ERROR |  Bundle Shutdown | RunnableTimedExecution           | oncurrent.RunnableTimedExecution  109 | Closing runnable for context OsgiBundleXmlApplicationContext(bundle=org.apache.servicemix.document, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs

      14:10:47,456 | ERROR |  Bundle Shutdown | RunnableTimedExecution           | oncurrent.RunnableTimedExecution  109 | Closing runnable for context OsgiBundleXmlApplicationContext(bundle=servicemix-camel, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs

      14:10:57,462 | WARN  |  Bundle Shutdown | ExtenderConfiguration            | al.support.ExtenderConfiguration  246 | Forcing the (internally created) taskExecutor to stop...

      14:10:57,463 | INFO  |  Bundle Shutdown | TimerTaskExecutor                | heduling.timer.TimerTaskExecutor  134 | Cancelling Timer

      14:10:57,464 | ERROR | x-camel-thread-1 | OsgiCamelJbiComponent            | icemix.common.AsyncBaseLifeCycle  358 | Error polling delivery channel

      javax.jbi.messaging.MessagingException: java.lang.InterruptedException

              at org.apache.servicemix.jbi.runtime.impl.DeliveryChannelImpl.accept(DeliveryChannelImpl.java:134)

              at org.apache.servicemix.common.AsyncBaseLifeCycle.pollDeliveryChannel(AsyncBaseLifeCycle.java:334)

              at org.apache.servicemix.common.AsyncBaseLifeCycle$1.run(AsyncBaseLifeCycle.java:319)

              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

              at java.lang.Thread.run(Unknown Source)

      Caused by: java.lang.InterruptedException

              at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(Unknown Source)

              at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source)

              at java.util.concurrent.ArrayBlockingQueue.poll(Unknown Source)

              at org.apache.servicemix.jbi.runtime.impl.DeliveryChannelImpl.accept(DeliveryChannelImpl.java:123)

              ... 5 more

       

      I googled a little and found out that the problem might possibly be related to spring deadlocking:

      http://www.mail-archive.com/dev@felix.apache.org/msg10167.html//www.mail-archive.com/dev@felix.apache.org/msg10167.html

      https://jira.springframework.org/browse/OSGI-611

       

      I'm currently using Fuse ESB 4.2 and cannot switch to 4.3 for reasons that (unfortunately) do not depend on me.

       

      Will be grateful for any tips on how to work this around.

       

      regards,

      peter