Recursive annotations cannot be deployed with JPA on Payara 5

[marvelous]

Description

---

When an annotation class annotated with itself gets scanned by EclipseLink, it enters into a recursive loop which triggers a StackOverflowError and fails the deployment. The same was working correctly on version 4.

Expected Outcome

Successful deployment

Current Outcome

A failed deployment with a log like in
https://javaee.groups.io/g/glassfish/topic/6519037
https://pastebin.com/61trs1kj

Steps to reproduce

Compile only these 3 files into a WAR and deploy in payara micro:

The culprit:

@Self
public @interface Self {}

The enabler:

<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.1" xmlns="http://xmlns.jcp.org/xml/ns/persistence">
        <persistence-unit name="persistence" transaction-type="JTA">
                <exclude-unlisted-classes>false</exclude-unlisted-classes>
        </persistence-unit>
</persistence>

The trigger:

@Singleton
public class Bean {
    @PersistenceContext
    private EntityManager em;
}

Samples

scce.zip

Context

I encountered the issue in a Kotlin project where kotlin.annotation.Target is annotated with itself.

Environment

• Payara Version: 5.181 and 5.182-SNAPSHOT
• Edition: Micro
• JDK Version: openjdk version "1.8.0_162"
• Operating System: Fedora release 26
• Database: default embedded H2 datasource

[smillidge]

Can you raise this on Eclipselink https://github.com/eclipse-ee4j/eclipselink?

[cristhiank]

I'm having a really hard time with this issue.
We are trying to migrate from Wildfly to Payara 5 but this is blocking us from being able to do it.
This is the line that triggers the infinite recursion.

I already saw the issue on eclipselink:
eclipse-ee4j/eclipselink#63

I will try to solve it and contribute the solution if I find a viable solution.

[cristhiank]

This is now fixed in upstream eclipse-ee4j/eclipselink#137 in both master and 2.7 branches.

[smillidge]

Created PAYARA-2881 to bring in the upstream fixes.