-
Notifications
You must be signed in to change notification settings - Fork 149
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
java.lang.LinkageError occured when lookup a remote EJB with multiple threads #23606
Comments
…emote EJB with multiple threads Signed-off-by: 11rx4f <ryosuke.okada@fujitsu.com>
…th multiple threads Signed-off-by: 11rx4f <ryosuke.okada@fujitsu.com>
I wrote a JMH test and reproduced it even on fixed version. I'm not sure yet, but my JMH test reproduces it reliably even in the first iteration. But when I called that just in the unit test, it passed. Bad there is not much logging and eclipse debugger wasn't able to trace it. |
I reproduced it in unit test also just by two consecutive calls of the method, but there was yet problem on another place - some generators bend the API and results are inconsistent; the class was generated, but cannot be loaded. |
So ... tests found another issue, I will close this and create a new one. This issue was about race condition which was fixed in the PR. |
- JMH test to reproduce race condition (already fixed) - tests for generator issues
- JMH test to reproduce race condition (already fixed) - tests for generator issues
Environment Details
GlassFish Version (and build number): Eclipse GlassFish 6.2.1 (build master-b577-g50d68a3 2021-09-01T02:07:52+0000)
JDK version: OpenJDK 11.0.12+7
OS: Red Hat Enterprise Linux release 8.0
Database:
Problem Description
java.lang.LinkageError occured when a remote EJB are lookuped with multiple threads.
Payara server seems to have fixed this problem as
payara/Payara#3087
Steps to reproduce
Impact of Issue
Cannot lookup remote EJB with multiple threads.
Additional info to reproduce this issue
LinkageError.zip
The text was updated successfully, but these errors were encountered: