-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug Report: [5.2021.9] @Stateless @Remote Bean causes java.lang.NoSuchMethodError during deployment /FISH-5933 #5500
Comments
I was able to reproduce a minimal test case that you can find here:
|
Hi @ctabin, I am experiencing BUILD FAILURE upon building the app. Also, can you 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. If you are looking for application support then please contact Payara Enterprise. |
Hi @shub8968, Thanks for your reply. Actually it fails on javadoc because it has to know your Here is the command I use to compile and run the test:
By default, the test fails because the version of Payara is 5.2021.9. You can see the Exception relative to the ClassLoader in the console. If you change the version to 5.2021.8 in the main |
Hi @ctabin, Please allow me some time. I'll update you soon. However, If you think you need to get it fixed to the earliest or need immediate action, I recommend you to consider Payara Enterprise. |
Hi @shub8968, Thanks for coming back. I just wanted to be sure that you could have a reproducer with the project since there wasn't any feedback. Thanks for the work and I'm looking for your update 👍 |
Greetings, @ctabin. After a detailed analysis of your reproducer, we have found that indeed the Payara Embedded API's deployment mechanisms trigger the error that you reported. We have escalated this issue to our Platform Development team in the form of the internal JIRA issue Since only the Payara Embedded distribution under JDK 11 is affected at the moment, this issue has been tagged with a low priority, so it will take some time until a proper fix is implemented. |
Hi @fturizo and thanks for your reply. Is there a possible workaround that we could apply (other than removing the |
I've raised a related upstream issue to replace |
@ctabin, as Steve clarified, the issue's cause is located upstream in the Gmbal PFL library, which needs to be patched out first, so at the moment there are no other workarounds. If this issue is critical on your end, I encourage you to get a Payara Enterprise subscription for your organisation so you can get a solution with celerity. |
Hi, thanks @smillidge to address the issue at the gmbal-pfl level. |
@fturizo FYI we were able to find a workaround, see this answer. And don't miss the system property |
G'day, I also had and independently solved this one with the same basic solution. The reason I am commenting is that I don't use Maven so I had to include pfl-basic-4.1.2 by hand in the library JAR list of my IDE project. The point is that pfl-basic-4.1.2 has to come before the embedded payara JAR or it has no effect. |
Description
Just by upgrading from version
5.2021.8
to5.2021.9
of payara-embedded-all, the deployment of our project crashes with the following stacktrace:Here is the full output of the server. Nothing else changed and all is working fine under the exact same conditions in version 5.2021.8.
EDIT: We were able to track down the source of the failure: actually it fails because of the following Bean:
If we remove either the
@Remote
OR the@Stateless
annotation, then it works fine (of course, that causes our application to crash further but that's expected because those annotations are needed).Hence it seems that the version 5.2021.9 doesn't support stateless beans that have to be exposed remotely. Note that if
@LocalBean
is commented out, still the same crash occurs.May be related to #5482 ?
Environment
The text was updated successfully, but these errors were encountered: