[FELIX-1753] The start level should check that the bundle still exists before starting it to avoid an ugly exception

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: framework-2.0.0
• Fix Version/s: framework-2.0.5
• Component/s: Framework
• Assignee: Richard S. Hall
• Reporter: Guillaume Nodet
• Created: 13/Oct/09 19:44
• Updated: 01/Apr/10 13:00
• Resolved: 25/Mar/10 06:02

Description

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.

Issue Links

• is duplicated by: FELIX-2064 Felix.setActiveStartLevel(int) throws error when it encounters an UNINSTALLED bundle