Bug Report: Failed to deploy war with @Stateless in Payara Micro 6.2023.7 / FISH-7722 #6337
Assignees
Labels
Status: Accepted
Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev
Type: Bug
Label issue as a bug defect
Comments
brunogptavares
added
Status: Open
|
Workaround: |
|
In PayaraMicro |
|
Same problem here. Thanks for the workaround @lprimak . In our case we also had to add |
|
Hi @brunogptavares, We have escalated this to the platform development team as Thank you, |
Elifzeynepedman
changed the title
Elifzeynepedman
added
Status: Accepted
|
Just to let y'all know, we see exactly this exception when using Payara Server Full Profile, JRE 17 and trying to deploy Dataverse (which is full of all sorts of EJBs). Please note that in the log, we see the typical "Portable JNDI names for EJB" outputs. After that, this exception is thrown: Adding the |
|
This (merged) PR has @luiseufrasio is it a fix for this issue (#6337)? Thanks. |
pdurbin
added a commit
to IQSS/dataverse
that referenced
this issue
Aug 18, 2023
|
same problem here using |
|
Same issue with Docker image String[] openModules = {
"java.base/java.io",
"java.base/jdk.internal.misc",
"java.management/javax.management.openmbean",
"java.management/javax.management"
};
addEnv("JVM_ARGS", Arrays.stream(openModules)
.map("--add-opens=%s=ALL-UNNAMED "::formatted)
.collect(Collectors.joining())); |
|
on 6.2023.9 I don't see this issue anymore and do not need the workaround |
Where did you apply this workaround ? Is it in pom.xml or elsewhere ? @avbravo |
|
I add it to the pom.xml file . @supersonic-potato <plugin>
<groupId>fish.payara.maven.plugins</groupId>
<artifactId>payara-micro-maven-plugin</artifactId>
<configuration>
<payaraVersion>${payara.version}</payaraVersion>
<deployWar>false</deployWar>
<commandLineOptions>
<option>
<key>--autoBindHttp</key>
</option>
<option>
<key>--deploy</key>
<value>${project.build.directory}/${project.build.finalName}</value>
</option>
</commandLineOptions>
<!--
JDK 17+ Soluciona error con EJB
-->
<javaCommandLineOptions>
<option>
<key>--add-opens</key>
<value>java.base/java.io=ALL-UNNAMED</value>
</option>
</javaCommandLineOptions>
</configuration>
<version>2.0</version>
</plugin> |
|
Current version doesn't need the add opens on So we still need to manually add This worked fine with previous versions. |
|
I see this with payara community edition, 6.2023.9 |
|
I see this issue still reproduces on Payara Micro 6.2023.9, and it seems because Payara Micro still doesn't have opens for |
|
Anyone else still facing that issue with payara micro 6.2023.9 despite applying the workaround on the pom.xml ? |
In case it is related to my previous post then I should clarify: I mean in my case Payara Micro 6.2023.9 with applied workaround by adding jvm-param starts and works well. What I'm saying that seems opens for |
|
Can confirm: No need for extra |
|
I can confirm that works well in Payara Micro 6.2022.10, i think is related to FISH-7817. |
Confirmed that with Payara Micro 6.2023.10 issue is resolved now. Thanks Payara Team! ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Brief Summary
Failed to deploy a Jakarta EE 10 aplication that have the anotation
@Statelessor@Singletonin Payara Micro 6.2023.7.Works fine in Payara-micro 6.2023.6.
Expected Outcome
The application should deploy and run normally.
Current Outcome
Reproducer
Just create a EJB class.
Operating System
Windows 11 Pro
JDK Version
Eclipse Temurim 17.0.4
Payara Distribution
Payara Micro
The text was updated successfully, but these errors were encountered: