[
https://issues.apache.org/jira/browse/FELIX-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754312#action_12754312
]
Karl Pauls commented on FELIX-1585:
-----------------------------------
Well, there are actually two unreleated things mixed-up in this issue. This
looks like a problem in SCR to me. Basically what happens is, the framework is
calling stop on the scr bundle which at the same time is trying to register a
service. The problem is that scr is holding a lock while it is trying to
register the service and it tries to acquire the same lock when the stop method
is called. As two different threads are doing the individual tasks we get a
deadlock.
This is a rather common problem and a good example of why one should avoid
holding a lock when calling into the framework. There is not much we can do
inside the framework so I'd say we should move this issue to scr and make it
about the deadlock and keep the other but mark it not as a bug but an
improvement.
> BundleException: Bundle xy cannot be started, since it is either starting or
> stopping. (on bundle update via FileInstall)
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-1585
> URL: https://issues.apache.org/jira/browse/FELIX-1585
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: felix-1.6.1, felix-1.8.1, felix-2.0.0
> Environment: Intel Core2Duo E6600, Windows XP SP3, Sun JVM
> 1.6.0_16-b01, Karaf SVN Trunk from 9.9.2009
> Reporter: Jeremias Maerki
> Attachments: thread-dump.txt
>
>
> Short description: Updating a bundle via FileInstall (file-system copy over
> an existing bundle with the same filename) can cause the following exception:
> "BundleException: Bundle xy cannot be started, since it is either starting or
> stopping."
> This happens in about 50% of all updates.
> Detailed problem description here: http://markmail.org/thread/odgiad76ioxm575y
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
