You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2014/02/03 13:58:08 UTC

[jira] [Created] (SLING-3365) HeartbeatHandler.deactivate() should not block

Stefan Egli created SLING-3365:
----------------------------------

             Summary: HeartbeatHandler.deactivate() should not block
                 Key: SLING-3365
                 URL: https://issues.apache.org/jira/browse/SLING-3365
             Project: Sling
          Issue Type: Bug
          Components: Extensions
    Affects Versions: Discovery Impl 1.0.2
            Reporter: Stefan Egli
            Assignee: Stefan Egli


We've seen a case where the HeartbeatHandler.deactivate() method was blocked at the synchronized(lock):

   java.lang.Thread.State: BLOCKED (on object monitor)
	at org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.deactivate(HeartbeatHandler.java:169)
	- waiting to lock <0x00000006028bcfd8> (a java.lang.Object)

This in turn prevented the bundle to be deactivated and blocked other felix code.

The deactivate() method should succeed quickly and instruct any other (HeartbeatHandler) thread to stop immediately too.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)