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 17476 - InvalidObjectException thrown while upgrading
Summary: InvalidObjectException thrown while upgrading
Status: CLOSED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Ant (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P1 blocker (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on: 17544
Blocks:
  Show dependency tree
 
Reported: 2001-11-09 14:52 UTC by Jan Lahoda
Modified: 2003-06-30 14:46 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Exception thrown. (1.82 KB, text/plain)
2001-11-09 14:55 UTC, Jan Lahoda 		Details
patch core-am-patch.jar (8.67 KB, application/octet-stream)
2001-11-09 16:48 UTC, Jan Pokorsky 		Details
New (annotated) exception. (1.96 KB, text/plain)
2001-11-09 16:55 UTC, Jan Lahoda 		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 Jan Lahoda 2001-11-09 14:52:52 UTC 
Attached exception was thrown while upgrading from 3.2.1 (98) to NB3.3 beta 1 or
200111090100. It looks pretty deterministic on my userdir, so I can attach it
here if necessary.
Comment 1 Jan Lahoda 2001-11-09 14:55:14 UTC 
Created attachment 3347 [details]
Exception thrown.
Comment 2 Jan Pokorsky 2001-11-09 16:45:00 UTC 
Culprit will be probably some filesystem trying to replace itself with 
null during serialization.

Please run upgrade again with following patch. It should provide more 
details about culprit.
Comment 3 Jan Pokorsky 2001-11-09 16:48:27 UTC 
Created attachment 3351 [details]
patch core-am-patch.jar
Comment 4 Jan Lahoda 2001-11-09 16:55:30 UTC 
Created attachment 3352 [details]
New (annotated) exception.
Comment 5 Jan Pokorsky 2001-11-09 17:19:34 UTC 
Aha org.apache.tools.ant.module.AntModule$GlobalJarFileSystem (see 
source, it is deprecated now) returns null in writeReplace. I'm not 
sure if AutomountSupport has to handle such cases or none filesystem 
can implement such behavior.
Comment 6 Jesse Glick 2001-11-09 20:23:16 UTC 
What should this filesystem do instead? It is quite useless (made
redundant by a layer entry) and needs to somehow delete itself during
a restore. I'm pretty sure writeReplace -> null did use to work before
AutomountSupport. Also I think the advice to do this is given in the
3.3 upgrade guide, this will have to be replaced if A.S. will not
handle nulls.
Comment 7 Jaroslav Tulach 2001-11-12 11:49:21 UTC 
I'll catch the exception in AutomountSupport.
Comment 8 Jaroslav Tulach 2001-11-12 11:52:04 UTC 
AutomountSupport rev. 1.35
Comment 9 Jesse Glick 2001-11-12 12:21:02 UTC 
Thanks, though the patch to AutomountSupport is a workaround, not a
real fix.

Fixing in the Ant module. The problem only seems to occur if the
ant-api.zip from the old installation still exists when you run the
new build, which is probably why this was not noticed before. I
changed also apisupport's installer in the same way. Note that the new
code is much more complex; it has to make several attempts to remove
the filesystem from the repository (it is added by the projects module
long after the filesystem is read). I changed also the 3.3 upgrade
guide to not recommend returning null from writeReplace.

committed   * Up-To-Date  1.10       
ant/src/org/apache/tools/ant/module/AntModule.java
committed   * Up-To-Date  1.48       
apisupport/src/org/netbeans/modules/apisupport/APIModule.java
Comment 10 Jan Lahoda 2001-11-13 12:08:22 UTC 
No exceptions thrown from 200111130100. Verified.
Comment 11 Quality Engineering 2003-06-30 14:46:43 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.