Re: SCR could not obtain state lock after 5 seconds

Hi David, So, with the last fix for FELIX-3639, I finally reproduced the initial deadlock problem. First, here is the "could not obtain lock" exception, including the root exception, showing the thread which is currently holding the writelock: --

[jira] [Updated] (FELIX-3557) Tests for DS circular dependency behavior

[ https://issues.apache.org/jira/browse/FELIX-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated FELIX-3557: Assignee: David Jencks > Tests for DS circular dependency behavior > --

[jira] [Updated] (FELIX-3625) "officially" upgrade scr to ds 1.2 from compendium 4.3

[ https://issues.apache.org/jira/browse/FELIX-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated FELIX-3625: Assignee: David Jencks > "officially" upgrade scr to ds 1.2 from compendium 4.3 > -

[jira] [Updated] (FELIX-3637) DS bind concurrency problem

[ https://issues.apache.org/jira/browse/FELIX-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated FELIX-3637: Assignee: David Jencks > DS bind concurrency problem > --- > >

[jira] [Updated] (FELIX-3559) [DS] first register immediate components' service, then create the implementation object per spec

[ https://issues.apache.org/jira/browse/FELIX-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated FELIX-3559: Assignee: David Jencks > [DS] first register immediate components' service, then create the >

[jira] [Resolved] (FELIX-3559) [DS] first register immediate components' service, then create the implementation object per spec

[ https://issues.apache.org/jira/browse/FELIX-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved FELIX-3559. - Resolution: Fixed > [DS] first register immediate components' service, then create the > imp

[DS] State of the bundle and ready for a release ?

Hi all, I saw quite some activity again recently around DS. I wonder what the state currently is and whether we should head for an early release before going into another round of fixes. I could imagine, we'd do a 1.6.2 release instead of 1.8.0 and do the 1.8.0 release once we are complete wit

Re: [DS] State of the bundle and ready for a release ?

I think I understand the cause of the currently known concurrency problems and hope to fix them in the next few days. If we don't see new problems for a week or so I'd be very happy to go for a 1.8.0 release. I'm not so thrilled about releasing the current code as it has an infrequent but majo

Re: [DS] State of the bundle and ready for a release ?

Hi, Am 29.08.2012 um 22:11 schrieb David Jencks: > I think I understand the cause of the currently known concurrency problems > and hope to fix them in the next few days. If we don't see new problems for > a week or so I'd be very happy to go for a 1.8.0 release. I'm not so > thrilled about