sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Egli (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SLING-3365) HeartbeatHandler.deactivate() should not block
Date Mon, 03 Feb 2014 14:14:09 GMT

     [ https://issues.apache.org/jira/browse/SLING-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stefan Egli resolved SLING-3365.
--------------------------------

    Resolution: Fixed

fixed, will be shipped with discovery.impl 1.0.4

> 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):
> {code}
>    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)
> {code}
> 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)

Mime
View raw message