Uploaded image for project: 'Felix'
  1. Felix
  2. FELIX-6451

After upgrading Event admin from 1.4.2 to 1.4.6, Thread blocked observed

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • eventadmin-1.4.4
    • None
    • Event Admin
    • None

    Description

      in 1.42 we have observed minor memory leak, so we have upgraded Event admin from 1.4.2 to 1.4.6 was Thread blocked observed, the issue still persist with the latest release of event admin.
       

      "pool-11-thread-9" #420 prio=5 os_prio=0 tid=0x0000000021c5e000 nid=0x42b4 waiting on condition [0x0000000035b3e000]"pool-11-thread-9" #420 prio=5 os_prio=0 tid=0x0000000021c5e000 nid=0x42b4 waiting on condition [0x0000000035b3e000]   java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for  <0x00000006c7bf4108> (a java.util.concurrent.Semaphore$NonfairSync) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037) at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328) at java.util.concurrent.Semaphore.tryAcquire(Semaphore.java:582) at org.apache.felix.eventadmin.impl.tasks.BlacklistLatch.awaitAndBlacklistCheck(BlacklistLatch.java:88) at org.apache.felix.eventadmin.impl.tasks.SyncDeliverTasks.execute(SyncDeliverTasks.java:125) at org.apache.felix.eventadmin.impl.handler.EventAdminImpl.sendEvent(EventAdminImpl.java:147) at org.apache.felix.eventadmin.impl.security.EventAdminSecurityDecorator.sendEvent(EventAdminSecurityDecorator.java:96) at com.thor.runtime.Deployer.postEvent(Deployer.java:1143) at com.thor.runtime.ApplicationHandler.postApplicationStateChangeEvent(ApplicationHandler.java:1323) at com.thor.runtime.ApplicationHandler.setState(ApplicationHandler.java:1141) at com.frwk.BWApplicationModuleImpl.stopApplication(BWApplicationModuleImpl.java:1077) at com.frwk.BWApplicationModuleImpl.handleEvent(BWApplicationModuleImpl.java:230) at com.thor.runtime.ApplicationEventRecorder.addEventListener(ApplicationEventRecorder.java:209) - locked <0x00000006c4384f48> (a com.thor.runtime.ApplicationEventRecorder) at com.frwk.BWApplicationModuleImpl.init(BWApplicationModuleImpl.java:1011) at com.frwk.BWModuleEventHandler.deployModule(BWModuleEventHandler.java:565) at com.frwk.BWModuleEventHandler.handleBundleEvent(BWModuleEventHandler.java:412) at com.thor.runtime.ApplicationHandler$1.call(ApplicationHandler.java:343) at com.thor.runtime.ApplicationHandler$1.call(ApplicationHandler.java:1) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
         Locked ownable synchronizers: - <0x00000006c7bf42f0> (a java.util.concurrent.ThreadPoolExecutor$Worker)

      "EventAdminThread #19" #71 daemon prio=5 os_prio=0 tid=0x0000000020e3e000 nid=0x1154 waiting for monitor entry [0x000000002decf000]   java.lang.Thread.State: BLOCKED (on object monitor) at com.thor.runtime.ApplicationEventRecorder.handleEvent(ApplicationEventRecorder.java:104) - waiting to lock <0x00000006c4384f48> (a com.thor.runtime.ApplicationEventRecorder) at org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:415) at org.apache.felix.eventadmin.impl.tasks.HandlerTask.run(HandlerTask.java:90) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
         Locked ownable synchronizers: - <0x00000006c36103c0> (a java.util.concurrent.ThreadPoolExecutor$Worker)

       

       

      this leads to deadlock like situation for us. 

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              adey03 Arijit Dey
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: