Bug Report: StackOverflowError due to Eclipselink loop ?

[AdolfGalland]

Brief Summary

Simple web application used as test case for jpa works fine with payara-6.2023.3.
Cannot deploy it on payara-6.2024.6, there is a StackOverflowError and the stack trace repeats the same lines lots of times.
Certainly related to bug 6568 ,closed for lack of information.
Stack trace of the exception taken from server log:
StackTrace.txt

Expected Outcome

The application should be deployed

Current Outcome

Application not deployed

Reproducer

The test application was created with Netbeans wizard "Jsf pages from entity classes", which is completely messed up, and partially corrected.
Here is the relevant part:
simple.zip

Operating System

Windows 11 pro

JDK Version

openjdk version "17.0.4.1"

Payara Distribution

Payara Server Full Profile

[Elifzeynepedman]

Hi @AdolfGalland,

Many thanks for bringing this issue to our attention.

Could you please provide a simple-to-follow scenario on how to reproduce this on the latest version? A reproducer should ideally follow the SSCCE rules: http://www.sscce.org/. It will greatly help us to find the cause and fix it.

Thank you,
Elif

[AdolfGalland]

In the first post I attached a very simple Netbeans project which deploys well on Glassfish and payara-6.2023.3, but fails on payara-6.2024.6. Don't know what to add.

[Elifzeynepedman]

Hi @AdolfGalland,

This project is neither a Maven nor a Gradle project and does not include an EAR or WAR file. To upload it to Payara, I manually created a WAR file. However, during deployment, I encountered the following error:

Error occurred during deployment: JNDI lookup failed for the resource: Name: [SimplerPU], Lookup: [portinerieDB], Type: [javax.sql.DataSource] -- Lookup failed for 'portinerieDB' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl, java.naming.factory.url.pkgs=com.sun.enterprise.naming}. Please see server.log for more details.

This error occurs because the project relies on an external portinerieDB data source that isn't configured within the project, leading to the JNDI lookup failure during deployment.

Could you please provide an reproducer that can be deployed on Payara Server without this issue?

Thank you,
Elif

[github-actions]

Greetings,
It's been more than 5 days since we requested more information or an update from you on the details of this issue. Could you provide an update soon, please?
We're afraid that if we do not receive an update, we'll have to close this issue due to inactivity.

[AdolfGalland]

Sorry, I cannot help. The problem is on persistence, in my environment I use Mysql. The example I provided uses a single table (entity), but it is necessary, it should exist and you need a connection pool and jdbc resource to access it. I can explain better what is needed, but I think some manual steps are inevitable to deploy the project.

[github-actions]

Greetings,
It's been more than 5 days since this issue was identified as abandoned.
We have closed this issue due to inactivity, please feel free to re-open it if you have more information to share.

[donalebro]

I had the same issues as @AdolfGalland, Replacing the Eclipse modules with 4.0.2 resolved the problem.