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