You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Jeremias Maerki (JIRA)" <ji...@apache.org> on 2009/09/11 21:38:58 UTC

[jira] Created: (FELIX-1585) BundleException: Bundle xy cannot be started, since it is either starting or stopping. (on bundle update via FileInstall)

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.8.1, felix-1.6.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.

[jira] Issue Comment Edited: (FELIX-1585) BundleException: Bundle xy cannot be started, since it is either starting or stopping. (on bundle update via FileInstall)

Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754309#action_12754309 ] 

Richard S. Hall edited comment on FELIX-1585 at 9/16/09 8:49 AM:
-----------------------------------------------------------------

I think this is just duplicating the other bug, no?

      was (Author: rickhall):
    I this is just duplicating the other bug, no?
  
> 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.

[jira] Commented: (FELIX-1585) BundleException: Bundle xy cannot be started, since it is either starting or stopping. (on bundle update via FileInstall)

Posted by "Rickard Öberg (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881071#action_12881071 ] 

Rickard Öberg commented on FELIX-1585:
--------------------------------------

We are using the version that comes with Glassfishv3, which seems to be 1.0.8. I'll try the latest jar (1.4.0) and see if that helps.

> 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: framework-1.6.1, framework-1.8.1, framework-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.

[jira] Commented: (FELIX-1585) BundleException: Bundle xy cannot be started, since it is either starting or stopping. (on bundle update via FileInstall)

Posted by "Karl Pauls (JIRA)" <ji...@apache.org>.
    [ 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.

[jira] Commented: (FELIX-1585) BundleException: Bundle xy cannot be started, since it is either starting or stopping. (on bundle update via FileInstall)

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880723#action_12880723 ] 

Felix Meschberger commented on FELIX-1585:
------------------------------------------

As Karl said, this might be a bug in Felix SCR holding a lock while calling into the framework (not a good thing).

What version of Felix SCR are you using ?

You might want to try a trunk build.

> 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: framework-1.6.1, framework-1.8.1, framework-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.

[jira] Commented: (FELIX-1585) BundleException: Bundle xy cannot be started, since it is either starting or stopping. (on bundle update via FileInstall)

Posted by "Rickard Öberg (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880711#action_12880711 ] 

Rickard Öberg commented on FELIX-1585:
--------------------------------------

We are using Glassfish/Felix with the FileInstall bundle to run out bundles. We are frequently seeing the above error, and it is so bad that we cannot work effectively. What happens is that we start Glassfish, and our bundles get deployed. Then we modify the code in one of the bundles, run Maven to get our jar, and copy it into Glassfish for redeploy. Then we get the above, quite often, and have to restart the server to get it sorted out.

Do you have any idea when this will be fixed?


> 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: framework-1.6.1, framework-1.8.1, framework-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.

[jira] Updated: (FELIX-1585) BundleException: Bundle xy cannot be started, since it is either starting or stopping. (on bundle update via FileInstall)

Posted by "Jeremias Maerki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeremias Maerki updated FELIX-1585:
-----------------------------------

    Attachment: thread-dump.txt

> 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.