felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-1753) The start level should check that the bundle still exists before starting it to avoid an ugly exception
Date Tue, 13 Oct 2009 21:17:31 GMT

    [ https://issues.apache.org/jira/browse/FELIX-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765235#action_12765235
] 

Richard S. Hall commented on FELIX-1753:
----------------------------------------

Well, we could change the log ERROR to a WARNING, but the whole point is we let start level
change process be a little loose so we don't run into any deadlocks. So, we just get all bundles
at the beginning while holding the lock and then cycle through them all starting/stopping
as appropriate without the lock.

> The start level should check that the bundle still exists before starting it to avoid
an ugly exception
> -------------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-1753
>                 URL: https://issues.apache.org/jira/browse/FELIX-1753
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: felix-2.0.0
>            Reporter: Guillaume Nodet
>
> ERROR: Error locking file:/Users/gnodet/work/felix/git/karaf/assembly/target/apache-felix-karaf-1.1.0-SNAPSHOT/deploy/test.xml
(java.lang.IllegalStateException: Bundle in unexpected state.)
> java.lang.IllegalStateException: Bundle in unexpected state.
> 	at org.apache.felix.framework.Felix.acquireBundleLock(Felix.java:4513)
> 	at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1048)
> 	at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
> 	at java.lang.Thread.run(Thread.java:613)
> This is the exception I have when i start felix after having removed a bundle managed
by fileinstall while felix was stopped.
> I think it should be easy enough to add a check to avoid this exception.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message