Bug 279596 - Problems using J9 Version 6 unpack
Summary: Problems using J9 Version 6 unpack
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Cross-Project (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: David Williams CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-09 07:34 EDT by Thomas Hallgren CLA
Modified: 2009-07-01 15:10 EDT (History)
2 users (show)

See Also:

Attachments
One of the files that J9 fails to unpack when using J9 V6. (35.80 KB, application/octet-stream)
2009-06-09 07:36 EDT, Thomas Hallgren CLA 		no flags Details
View All 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 Thomas Hallgren CLA 2009-06-09 07:34:28 EDT 
I'm not able to unpack some files containing nested jars using the J9 JDK installed at /shared/common/ibm-java-ppc-604. The same files can be unpacked with /shared/common/ibm-java2-ppc-50 without problems. What's perhaps even more remarkable is that I can unpack the file using a Sun JDK Version 6.

It's *only* the J9 V6 that fails and it will only fail on the nested files. Several other bundles in the same distribution, packed and signed in the same way, are unpacked without problems.

The nested files have been packed using -E4. I've tried using default too and it doesn't make any difference.
Comment 1 Thomas Hallgren CLA 2009-06-09 07:36:25 EDT 
Created attachment 138663 [details]
One of the files that J9 fails to unpack when using J9 V6.
Comment 2 David Williams CLA 2009-06-09 08:22:32 EDT 
I think this has been reported before, in bug 244603, and is specific to PPC version.
Comment 3 Nick Boldt CLA 2009-06-09 10:25:46 EDT 
Workaround: prevent the pack200 process from packing nested jars. 

Stick this in the plugin's META-INF/eclipse.inf file:

# Exclude children of this jar from signing and packing
jarprocessor.exclude.children=true

Ref: http://wiki.eclipse.org/JarProcessor_Options
See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=279056
Comment 4 Thomas Hallgren CLA 2009-06-09 10:56:50 EDT 
(In reply to comment #3)
> Workaround: prevent the pack200 process from packing nested jars. 
> 
In that case it's probably better to skip the pack200 of these jars altogether since all .class files reside in the nested jars.

In case someone closer to build.eclipse.org than I am (and can run the debugger with reasonable response times) would like to track this down, I've set up a test environment where the problem is easy to reproduce:

Log in to the build machine:

bash> cd /opt/public/tools/buckminster/bug279596
bash> . ./test.env
bash> ant

The build.xml contains a commented out jvmarg for remote debugging (line 85).

What really nags me is that it only affects the nested jars. Why not all of them? Is there some different handling of unpack when P2 unpacks nested jars?
Comment 5 David Williams CLA 2009-07-01 15:10:34 EDT 
Its not obvious from reading bug 244603, but I think this is same bug as that one. 

I tried your test case with the SR5 version of IBMs PPC Java 6 VM and it works fine in my testing (and did fail with the SR4 version). 

I've put a copy of SR5 in 
/shared/common/ibm-java-ppc-605