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

Richard S. Hall edited comment on FELIX-1753 at 10/13/09 3:24 PM:
------------------------------------------------------------------

I am not against that, but, to be clear, that doesn't eliminate the 
possibility, it just shortens the window in which it can happen.

We could also log just the message and not the exception, since that is more of 
an implementation detail anyway.

      was (Author: rickhall):
    I am not against that, but, to be clear, that doesn't eliminate the 
possibility, it just shortens the window in which it can happen.

We could also likely not log the exception, since that is more of an 
implementation detail anyway.
  
> 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.

Reply via email to