Bug Report: CDI deployment failure. "Unknown BDAType: UNKNOWN" #7214
Assignees
Labels
Status: Open
Issue has been triaged by the front-line engineers and is being worked on verification
Type: Bug
Label issue as a bug defect
Comments
TheOnlyAl
added
Status: Open
|
Great reproducer, thanks! |
|
Hi. I tried your Payara (https://nexus.hope.nyc.ny.us/repository/maven-releases/fish/payara/distributions/payara/6.2025.2-2/payara-6.2025.2-2.zip) build for my deployment (not the reproducer), and now i get a different exception. Is this maybe another bug or related to this? |
|
I just checked and the reproducer will also generate this error. It seems to happen when getPostConstructDescriptorByClass(String className, JndiNameEnvironment jndiNameEnv) is called with |
|
Please be patient. I have not figured this one out yet |
|
Thank you for your reproducer and your patience. Thank you |
|
Hi. I did not intend to pressure you in any way and I just tried to provide as much information as possible. I am thankful for your work! Sadly it seems that your fix did not fix the |
|
Seems I found the problem. You just need to have an EJB module in the EAR file. This will produce the error from above. |
|
Thank you for your quick turn-around and reproducer as well. This is very helpful. Also, I am sorry for the bit of a short-term pain, but in the long-term, this is leading to #7165 performance, Honestly I am pretty shocked that EARs are used that widely with the newest versions of Payara. It's a a good sign. |
|
The good news: Deployment works now for both my applications under test. The problem in the app from above is when i call a REST Service which I am still trying to update the reproducer but somehow it is rather tricky. But maybe you will already have an idea. |
|
I found some way to reproduce a similar problem. I just added some bean validation to an EJB: If you deploy this and visit: {payaraHost}/cdi-unknownbda-war-cdi/ you will get an error: |
|
Thank you! Looks like a similar issue to the last one. I'll go through that file to make sure that I get all similar code paths. |
|
I think we are getting close. Thanks again for the help and quick turnaround. |
|
Well, it seems that did it. Deployment seems fine and i used/tested the deployed Application for a few minutes and no injection error happened! I will come back if something will pop up, otherwise it seems to be fixed. Thanks! |
|
Thanks for all your help tracking this down. It was not easy. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Brief Summary
Deployment of an EAR fails on Payara 6.2025.2 for a certain configurations:
One example is:
EAR
|- WAR (Only Static files. No CDI)
|- WAR-CDI (With CDI)
|- lib/JAR (With CDI)
Seems this Bug was introduced in #7032 @lprimak
Expected Outcome
Deployment should not fail.
Current Outcome
Deplyoment fails with error from above.
Reproducer
https://github.com/TheOnlyAl/cdi-unknownbda
Tested with Maven 3.9.9.
Build the project and try to deploy the ear file: cdi-unknownbda-ear-1.0.0.ear
The produced EAR can be deployed using Payara 6.2025.1. With version 6.2025.2 it fails.
Hope this helps.
Operating System
Docker with WSL and Windows 10
JDK Version
JDK 17
Payara Distribution
Payara Server Full Profile
The text was updated successfully, but these errors were encountered: