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.

Bug 14172 - IndexOutOfBoundsException when files deleted outside netbeans
Summary: IndexOutOfBoundsException when files deleted outside netbeans
Status: CLOSED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcscore (show other bugs)
Version: 3.x
Hardware: PC Other
: P4 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
: 13620 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-08-03 12:33 UTC by support
Modified: 2003-07-01 12:56 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Exceptions thrown while canceling RMI object. (3.03 KB, text/plain)
2001-08-08 14:49 UTC, Jiri Kovalsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description support 2001-08-03 12:33:14 UTC
I'm using the VCS Generic support with Clearcase (though I'm not sure if the 
problem isn't actually in vcscore).  There were a bunch of view local files 
(not under Clearcase control) in the Explorer under the Clearcase mounted 
filesystem.  I deleted some of the from a Command Prompt (none of which were 
open in netbeans' editor at the time), and a few seconds later netbeans 
produced the following exceptions:

Fri Aug 03 11:57:36 BST 2001: java.lang.IndexOutOfBoundsException: Index: 0, 
Size: 0
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
        at java.util.ArrayList.RangeCheck(ArrayList.java:491)
        at java.util.ArrayList.get(ArrayList.java:307)
        at 
org.netbeans.modules.vcscore.caching.RefreshCommandSupport.getAttribute
(RefreshCommandSupport.java:458)
        at 
org.netbeans.modules.vcscore.caching.RefreshCommandSupport.getStatusAnnotation
(RefreshCommandSupport.java:401)
        at org.netbeans.modules.vcscore.VcsFileSystem.annotateName
(VcsFileSystem.java:1631)
        at org.openide.loaders.DataNode.getDisplayName(DataNode.java:147)
        at org.openide.nodes.FilterNode.getDisplayName(FilterNode.java:247)
        at org.openide.explorer.view.VisualizerNode.<init>
(VisualizerNode.java:126)
        at org.openide.explorer.view.VisualizerNode.getVisualizer
(VisualizerNode.java:69)
        at org.openide.explorer.view.VisualizerChildren.added
(VisualizerChildren.java:65)
        at org.openide.explorer.view.VisualizerEvent$Added.run
(VisualizerEvent.java:83)
        at org.openide.explorer.view.VisualizerNode$QP.run
(VisualizerNode.java:442)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:154)
[catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:337)
        at java.awt.EventDispatchThread.pumpOneEventForHierarchy
(EventDispatchThread.java:131)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy
(EventDispatchThread.java:98)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:85)

a couple of times, followed by a number of

Fri Aug 03 12:31:45 BST 2001: java.util.NoSuchElementException: null
java.util.NoSuchElementException
        at java.util.LinkedList$ListItr.next(LinkedList.java:478)
        at org.openide.explorer.view.VisualizerChildren.removed
(VisualizerChildren.java:98)
        at org.openide.explorer.view.VisualizerEvent$Removed.run
(VisualizerEvent.java:111)
        at org.openide.explorer.view.VisualizerNode$QP.run
(VisualizerNode.java:442)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:154)
[catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:337)
        at java.awt.EventDispatchThread.pumpOneEventForHierarchy
(EventDispatchThread.java:131)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy
(EventDispatchThread.java:98)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:85)
Comment 1 Martin Entlicher 2001-08-03 13:26:39 UTC
*** Issue 13620 has been marked as a duplicate of this issue. ***
Comment 2 Martin Entlicher 2001-08-03 13:41:47 UTC
This problem was already reported by someone (but I can not find an
issue for it). It's already fixed in development builds.
BTW: you are right, that the bug is actually in vcscore.
Comment 3 Jiri Kovalsky 2001-08-08 14:37:07 UTC
I have to unfortunately reopen the bug because it still occurs in the 
latest development build #200108080100 of NetBeans 3.3 and reproducti-
on in Forte for Java 3.0 FCS is quite easy.

1. Mount CVS filesystem using Command-line Client.
2. Create new RMI_Object using "New|RMI|UnicastRemoteServer (group)"
   in the root of your CVS filesystem.
3. Close the editor and "Compile" "RMI_ObjectImpl [Local]" node.
4. Do "CVS|Refresh" on the root of your CVS filesystem.
5. Invoke "Tools|Cancel RMI" on "RMI_ObjectImpl [Local]" node.
6. Exception should appear after a while.
7. If you are not successful with reproduction delete all RMI_Object*
   files externally, wait until they disappear from FS and repeat it.

For more details have a look at the exceptions attached.
Comment 4 Jiri Kovalsky 2001-08-08 14:49:55 UTC
Created attachment 2101 [details]
Exceptions thrown while canceling RMI object.
Comment 5 Martin Entlicher 2001-08-09 18:05:43 UTC
Well, it should be fixed in dev builds. I can not reproduce it any
more.
Comment 6 Jiri Kovalsky 2001-10-23 16:54:02 UTC
I did various hanky-panky but was not able to reproduce the exception 
so I guess it got fixed. Verified in development build of NetBeans 3.3
#200110230735.
Comment 7 Martin Entlicher 2001-12-04 16:23:11 UTC
Addind Petr on CC, since users complain about this on
nbusers@netbeans.org.
Comment 8 Jiri Kovalsky 2001-12-05 13:10:10 UTC
[FFJ CUSTBUG]
This bug should be included in the next jumbo patch since at least 3 
external users have encountered it.
Comment 9 Jiri Kovalsky 2002-01-29 13:52:46 UTC
Exception is never thrown again but if RMI object is canceled all
class fileobjects don't work together with VCS filesystem. Due to
missing sta-
tus information it seems like annotateName() is not called. Popup menu
is shown but no action can be invoked and those class files can't be
version controlled anyhow. Could somebody from Sustaining team
investigate it ?
Comment 10 dmladek 2002-01-31 15:24:20 UTC
No comments from sustaining guys...seems like whisper fix:-/
Well, No E. is thrown,
but problems with unaccessible CVS actions/commands still persist
(tested with JP)
Comment 11 Quality Engineering 2003-07-01 12:56:47 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.