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 47612 - [40cat] Illegal Argument Exception: invalid constant pool type: 13
Summary: [40cat] Illegal Argument Exception: invalid constant pool type: 13
Status: RESOLVED DUPLICATE of bug 47438
Alias: None
Product: java
Classification: Unclassified
Component: Classfile (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-20 23:54 UTC by thunderjon
Modified: 2004-08-21 21:09 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IDE log (228.22 KB, text/plain)
2004-08-20 23:55 UTC, thunderjon 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description thunderjon 2004-08-20 23:54:48 UTC 
[ BUILD # : 200408191352 ]
[ JDK VERSION : J2SE 1.4.2_05 ]

I am able to reproduce this at will...

1. Have a web project imported and CVS'd.

2. Attempted to CVS remove a folder (META-INF). This horks but may be a separate bug since from what I can tell it is empty on CVS server and when I try to remove it it deletes my local but fails to remove from CVS.

3. [OPTIONAL STEP] I then open and close some class folders and soon enough the system chugs and presto, exception.

I suspect that #47438 is somehow related.
Comment 1 thunderjon 2004-08-20 23:55:59 UTC 
Created attachment 17005 [details]
IDE log
Comment 2 Marian Mirilovic 2004-08-21 09:33:37 UTC 
java.lang.IllegalArgumentException: invalid constant pool type: 13
	at
org.netbeans.modules.classfile.ConstantPool.getConstantPoolEntry(ConstantPool.java:236)
Comment 3 _ tball 2004-08-21 21:09:04 UTC 
This exception is (or was) thrown when a bad constant pool is
referenced, which probably happened when CVS "horked".  The
IllegalArgumentException is now caught during classfile loading, and
an IOException is thrown instead, which the ClassUpdater (should)
handle properly.

*** This issue has been marked as a duplicate of 47438 ***