Why is this method reference failing at runtime but not the corresponding lambda call?

Question

I have these two interfaces. One is public (A), the other one is package private (AA). A extends AA.

package pkg.a;

@FunctionalInterface
public interface A extends AA {

}

.

package pkg.a;

interface AA {

    default void defaultM() {
        System.out.println(m());
    }

    String m();
}

I have this code (in a different package):

package pkg;

import java.util.Arrays;
import java.util.List;

import pkg.a.A;

public class Test {

    public static void main(String[] args) {
        List<A> list = Arrays.asList(() -> "imp1", () -> "imp2");

        list.stream().forEach(a -> a.defaultM());
        list.stream().forEach(A::defaultM);
    }
}

When running the above code the list.stream().forEach(A::defaultM); throws the below exception. Why? Why can't the method reference access the methods defined in the package-private interface while the lambda expression can? I'm running this in Eclipse (Version: 2018-12 (4.10.0)) with Java version 1.8.0_191.

imp1
imp2
Exception in thread "main" java.lang.BootstrapMethodError: call site initialization exception
    at java.lang.invoke.CallSite.makeSite(CallSite.java:341)
    at java.lang.invoke.MethodHandleNatives.linkCallSiteImpl(MethodHandleNatives.java:307)
    at java.lang.invoke.MethodHandleNatives.linkCallSite(MethodHandleNatives.java:297)
    at pkg.Test.main(Test.java:14)
Caused by: java.lang.IllegalArgumentException: java.lang.IllegalAccessException: class is not public: pkg.a.AA.defaultM()void/invokeInterface, from pkg.Test
    at java.lang.invoke.MethodHandles$Lookup.revealDirect(MethodHandles.java:1360)
    at java.lang.invoke.AbstractValidatingLambdaMetafactory.<init>(AbstractValidatingLambdaMetafactory.java:131)
    at java.lang.invoke.InnerClassLambdaMetafactory.<init>(InnerClassLambdaMetafactory.java:155)
    at java.lang.invoke.LambdaMetafactory.metafactory(LambdaMetafactory.java:299)
    at java.lang.invoke.CallSite.makeSite(CallSite.java:302)
    ... 3 more
Caused by: java.lang.IllegalAccessException: class is not public: pkg.a.AA.defaultM()void/invokeInterface, from pkg.Test
    at java.lang.invoke.MemberName.makeAccessException(MemberName.java:850)
    at java.lang.invoke.MethodHandles$Lookup.checkAccess(MethodHandles.java:1536)
    at java.lang.invoke.MethodHandles$Lookup.revealDirect(MethodHandles.java:1357)
    ... 7 more

This is a really well-asked question. It has a minimal reproducible example (which replicates the error for me even in JDK 8), it's clear... Nice to see! — T.J. Crowder
– T.J. Crowder, Commented Sep 2, 2019 at 10:47
@AndrewTobilko - It compiles, but it doesn't run (for me in JDK 8 [what I have handy], specifically 1.8.0_74 using "Java HotSpot(TM) 64-Bit Server VM (build 25.74-b02, mixed mode)"). "Exception in thread "main" java.lang.IllegalAccessError: tried to access class pkg.a.AA from class pkg.Test" — T.J. Crowder
– T.J. Crowder, Commented Sep 2, 2019 at 10:47
It runs for me in "openjdk version "11.0.1" 2018-10-16" using "OpenJDK 64-Bit Server VM 18.9 (build 11.0.1+13, mixed mode)". Sounds like a bug that's been fixed. — T.J. Crowder
– T.J. Crowder, Commented Sep 2, 2019 at 10:50
Updated question with the Java version used. Will try with a later java version and report back. — etxalpo
– etxalpo, Commented Sep 2, 2019 at 10:58
This seems to be the same as bugs.eclipse.org/bugs/show_bug.cgi?id=480930 (from 2015... ), and there are some related issues in javac linked from that one. — Marco13
– Marco13, Commented Sep 2, 2019 at 11:37

Oleksandr Pyrohov · Accepted Answer · 2019-09-02 11:46:16Z

4

This is a bug:

Method reference uses wrong qualifying type.

A reference to a method declared in a package-access class (via a public subtype) compiles to a lambda bridge; the qualifying type in the bridge method is the declaring class, not the referenced class. This leads to an IllegalAccessError.

Fixed in Java 9.

answered Sep 2, 2019 at 11:46

Oleksandr Pyrohov

16.5k6 gold badges76 silver badges99 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

T.J. Crowder · Accepted Answer · 2019-09-02 10:57:20Z

This appears to be a bug in certain Java versions.

I can replicate it if I compile and run it with JDK 8, specifically:

tj$ javac -version
javac 1.8.0_74
tj$ java -version
java version "1.8.0_74"
Java(TM) SE Runtime Environment (build 1.8.0_74-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.74-b02, mixed mode)

...but not with JDK 11 or 12, specifically:

tj$ javac -version
javac 11.0.1
tj$ java -version
openjdk version "11.0.1" 2018-10-16
OpenJDK Runtime Environment 18.9 (build 11.0.1+13)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.1+13, mixed mode)

and

tj$ javac -version
javac 12.0.2
tj$ java -version
java version "12.0.2" 2019-07-16
Java(TM) SE Runtime Environment (build 12.0.2+10)
Java HotSpot(TM) 64-Bit Server VM (build 12.0.2+10, mixed mode, sharing)

I can also replicate it if I compile with JDK 8 but run it with JDK 12's runtime, suggesting a compilation problem.

Collectives™ on Stack Overflow

Why is this method reference failing at runtime but not the corresponding lambda call?

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related