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 12139 - Compiling a copied jarContent causes zip exception
Summary: Compiling a copied jarContent causes zip exception
Status: CLOSED INVALID
Alias: None
Product: obsolete
Classification: Unclassified
Component: jarpackager (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P2 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-05-12 03:40 UTC by John Baker
Modified: 2003-07-01 10:02 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 John Baker 2001-05-12 03:40:08 UTC 
Using kit 010510 on Solaris

To reproduce:

1) Mount a new webmodule, "wm"
2) Mount a directory, "parent"(parent of the webmodule)
3) Create a package in "parent"
4) Create a new dbschema and generate java in parent's package
5) Create a new jar content for the package such that the jar file is to
   be created in the WEB-INF/lib directory of "wm"
6) Compile jar content
7) Copy jar content to WEB-INF/lib of "wm"
8) Compile jar content in this new location

Result:
Fri May 11 19:30:40 PDT 2001: java.lang.InternalError: Posted StackTrace
Annotation: Exception occurred in Request Processor
Nested annotation: jzentry == 0
org.openide.util.RequestProcessor$Holder: Posted StackTrace(task
org.openide.filesystems.JarFileSystem$1@267f96 [-84, 1, -1])
        at
org.openide.util.RequestProcessor$Task.createHolder(RequestProcessor.java:322)
        at org.openide.util.RequestProcessor.post(RequestProcessor.java:100)
        at org.openide.util.RequestProcessor.post(RequestProcessor.java:84)
        at org.openide.filesystems.JarFileSystem$2.run(JarFileSystem.java:241)
        at org.openide.util.Task.run(Task.java:124)
[catch] at
org.openide.util.RequestProcessor$ProcessorThread.run(RequestProcessor.java:626)
 
Fri May 11 19:30:40 PDT 2001: java.lang.InternalError: jzentry == 0
java.lang.InternalError: jzentry == 0
        at java.util.zip.ZipFile$2.nextElement(ZipFile.java:297)
        at java.util.jar.JarFile$1.nextElement(JarFile.java:198)
        at org.openide.filesystems.JarFileSystem$1.run(JarFileSystem.java:130)
        at org.openide.util.Task.run(Task.java:124)
[catch] at
org.openide.util.RequestProcessor$ProcessorThread.run(RequestProcessor.java:626)


Note: this exception also occurred on Windows.

Also, 3 times the IDE core dumped, but not consistently reproducible.
I have the core file, dbschema and generated java if necessary.
Comment 1 John Baker 2001-05-12 03:41:56 UTC 
I wasn't able to reproduce this _without_ using a web module and TP classes,
it seems both are necessary.
Comment 2 Mike Schilling 2001-05-14 17:17:41 UTC 
As you can see from the stack trace, the jar file has been mounted as a jar file 
system and that is the source of the error.  The jar packager never does this.  
It can happen in one of two ways: 1. By the user explicitly mounting the jar 
file in the IDE.  2.  By code other than the jar packager.

Since you don't mention doing this in the instructions for reproducing the bug, 
and since you need both web and TP to get the error, it must be the latter.  Web 
has already fixed one bug in this area (4449058).  Please re-enter this as a bug 
against web or TP (or both).
Comment 3 Quality Engineering 2003-07-01 09:57:52 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.
Comment 4 Quality Engineering 2003-07-01 10:02:06 UTC 
Resolved for 3.4 or earlier, no new info since then -> closing.
Comment 5 Quality Engineering 2003-07-01 10:02:56 UTC 
Resolved for 3.4 or earlier, no new info since then -> closing.