JDK-5049767 : REGRESSION: Bug 4825523 is failed for 1.4.2_05-b02
  • Type: Bug
  • Component: other-libs
  • Sub-Component: other
  • Affected Version: 1.4.2_05
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux_suse_sles_8
  • CPU: x86
  • Submitted: 2004-05-19
  • Updated: 2013-08-07
  • Resolved: 2004-05-20
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.2_05 05Fixed
Related Reports
Relates :  
Description
Bug 4825523 is failed for 1.4.2_05-b02, but passed for 1.4.2_05-b01 on SuSE SLES-8.1. 

How to reproduce:
----------------

Run 4825523 testcase under regression workspace (/net/shiva.sfbay/test/MyTestArea/JDK1.4.2/workspace_142/test/CTE_REGTEST/Generic/4825523). you will see the following output.

Behavior with 1.4.2_05-b02:
--------------------------

/usr/j2sdk1.4.2_05/bin/java -version 
java version "1.4.2_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b02)
Java HotSpot(TM) Client VM (build 1.4.2_05-b02, mixed mode)

/usr/j2sdk1.4.2_05/bin/java -jar test.jar 
Invalid or corrupt jarfile test.jar

Behavior with 1.4.2_05-b01:
--------------------------

/export/updates/regressions/j2sdk1.4.2_05/bin/java -version
java version "1.4.2_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b01)
Java HotSpot(TM) Client VM (build 1.4.2_05-b01, mixed mode)

/usr/j2sdk1.4.2_05/bin/java -jar test.jar 
Exception in thread "main" java.lang.NoSuchMethodError: main
(Which is expected Exception by the testcase)
###@###.### 2004-05-19

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.2_05 FIXED IN: 1.4.2_05 INTEGRATED IN: 1.4.2_05
14-06-2004

EVALUATION Seems like unjar the test.jar file and rejar it again solves the problem. I've tested the new .jar file on Sol sparc, SuSE8.2 on amd64, RH7.3 and passed with 142_05 b01, b02, latest nightly builds and latest tiger builds. Definitely some fix went into 142_05 b02 that changed the working jar file to a 'Invalid or corrupt jarfile'. While investigating the new behaviour in 142_05 b02, changing category/subcatetory to java/cte-test and fix the problem. ###@###.### 2004-05-19
19-05-2004