> I'm getting the exception below when I
> try to start my app with netbeans, after a few successful attempts.  Looks
> like a problem reading the cache, but can we avoid letting these kinds
> of exceptions cause startup to fail?  Is there anything we can do to,
> for instance, catch them and just rebuild the cache if we detect that it
> is corrupted?
> 
> Note that it's possible that I used control+C at the console to
> terminate the my app instance after one of the successful startup
> attempts, and that could well be the reason for the corrupted cache.
> Nevertheless, we shouldn't allow something like this to prevent startup
> from succeeding on subsequent runs.
> 
> Aug 3, 2010 1:18:59 PM org.netbeans.core.startup.ModuleList readInitial
> WARNING: null
> java.io.EOFException
>     at
> java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.j
> ava:2554) at
> java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at
> java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at
> org.netbeans.core.startup.ModuleList.readCache(ModuleList.java:633) at
> org.netbeans.core.startup.ModuleList$ReadInitial.run(ModuleList.java:1497)
>     at
> org.openide.filesystems.EventControl.runAtomicAction(EventControl.java:125)
>     at
> org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:542)
>     at
> org.netbeans.core.startup.ModuleList.readInitial(ModuleList.java:168) at
> org.netbeans.core.startup.ModuleSystem.readList(ModuleSystem.java:272)
>     at org.netbeans.core.startup.Main.getModuleSystem(Main.java:171)
>     at org.netbeans.core.startup.Main.start(Main.java:302)
>     at
> org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:114) at
> java.lang.Thread.run(Thread.java:619)