JDK-8008770 : SerializedLambda incorrect class loader for lambda deserializing class
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang.invoke
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2013-02-23
  • Updated: 2013-06-25
  • Resolved: 2013-02-26
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.
JDK 8
8 b82Fixed
Related Reports
Relates :  
JDK-8008356 - Test java/lang/invoke/lambda/LambdaSerialization.java failing
Description
If the class loader is different, failures are seen. 

This is seen in deserialization tests run in -samevm mode and the in submitted attached example (thanks Peter)

It has been verified that the attached patch fixes the test failures.
Comments
Original code used thread context class loader, which may not be the correct loader for the class. This shows up in tests as class not found. Fix being reviewed serializes the class rather then the class name in the SerializedLambda.
25-02-2013