This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Product Version = NetBeans IDE Development Version (Build 200202190100) IDE Versioning = IDE/1 spec=2.3 impl=200202190100 Operating System = Linux version 2.4.10 running on i386 Java; VM; Vendor = 1.4.0; Java HotSpot(TM) Client VM 1.4.0-b92; Sun Microsystems Inc. Java Home = /usr/java/j2sdk1.4/sun/jdk1.4/jre System Locale; Encod. = cs_CZ; ISO-8859-2 ================================================================================= I'm using Gen-cvs FS for a long time. There were some changes in definition of commands in cvs profile...thus sometimes I've received IAE: File name element is missing Martin adviced me to customize FS: change profile to another one and back. This I've done it. But IAE is still SOMETIMES occures in little bit different form (in Required Processor). I can't attache output of cvs->update 'cause it is dummy in Runtime TAB ->history commands. Just only stacktrace of IllegalArgumentException
Created attachment 4744 [details] stacktrace of IAE
It seems, that your cache file on disk (CVS/netbeans.cmd.cache) is corrupted. The exception occurs while reading from the disk cache. I'll try to make it more robust and handle the exception in disk cache reading process.
Fixed in dev build Mar 14. The IllegalArgumentException is catched and reported into ide.log via ErrorManager, but everything goes on.
Dane, please take a look at this bug since it is your special Linux box dependent ... :-) Thanks.
OK....IT behaves exactly you wrote Martin;-) BTW:Jirka, I don't think so that it's linux dependend issue (it might be confusing for users;).
Martin, sorry I'm reopening this issue. (I might start a new one, but prefer to stay in this one , at least we have everything together;) Now it's: ENHANCEMENT and P4 (cause it might be very easy to fix it,IMHO;-) Frankly speaking, Once I done cvs->update on my FS and into ide.log is written so many IAEs...that's because I have too many corrupted cache files on a disk. That's right... But I suppose next time of running cvs->update no IAE. will be written into ide.log. But they appeare again in the ide.log:-( It means that the cache files after first run of UPDATE are not repaired/rewritten... And that I think is a bug.... I don't have any control of this.... ------------------------------------------------------------------- So my idea is: if you'll be so kind and put there some more information into the stacktrace: Which cache file it was corrupted... To have the control if next time I do the update it didn't throw again an the same file IAE.
The full path of the affected cache file added to the exception annotation. This should help to track down the problem, that is associated with IO. Fixed in dev build May 17.
yea, think I sow the improved stacktrace in todays build
Resolved for 3.4.x or earlier, no new info since then -> closing.