-
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
NPE when get result from JCache - @CacheResult #5000
Comments
Hi @ciment7, can you please try to reproduce this issue in the latest version of Payara Community? (5.2020.6) Please also provide a reproducer ideally following the SSCCE rules: http://www.sscce.org/. It will greatly help us to find the cause and fix it. |
I think this will be fixed when this PR (or it's subsets) are merged: #4762 |
yes of course, I will try to reproduce this bug on the latest version of Payara Community. I will notify you then. Thanks. |
Hi @ciment7, do you have any updates on the status of the reproducer? |
#5010 should fix this issue |
Hi, I can not reproduce NPE on my local machine or test environment. I don`t have any idea how to reproduce NPE. I wrote stress test, but without the exceptions. |
Hi @ciment7, Without a way of reproducing this issue reliably, I will have to close it. @lprimak believes #5010 will resolve this issue, so I recommend to wait until that is implemented and released and to try to see if it alleviates your problems. Feel free to reopen the issue if you find a simple way of reproducing the problem. Thank you, |
Description
Hi,
I`m running war application on payara 5.201 (Jakarta EE 8). Sometimes (usually when the application is under heavy load) I got this exception:
This exception I get when I hit cache by JCache API - @CacheResult. I use multiple payara nodes clustered with multicast options.
This is my snippet of code:
Expected Outcome
It should never throw exception :)
Current Outcome
Less than 1% of all requests finish with exception.
Steps to reproduce (Only for bug reports)
When the cache is under heavy load.
Environment
The text was updated successfully, but these errors were encountered: