-
Notifications
You must be signed in to change notification settings - Fork 47
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
NullPointer #64
Comments
@iainstarks I can certainly see the bug that caused the initial error. The second error is 'harmless' although it may be a symptom of others things happening. I'm not fully confident that the bug that caused the initial error is also the cause of the subsequent exceptions however. If you could describe more about how you use the cache that might help. In particular:
If you could upload a full set of logs somewhere so I can look through them that might be useful too. In the meantime I can build you a copy of Ehcache 3 with this first fix applied, and we can cross out fingers that I'm missing something and this does fix both problems. |
Hi Chris, LocationCheckType is an enum The list will usually be empty or have a single entry. I think a log will be small enough to email. I'll try that. |
Drop me an email to iainstarks@gmail.com and I'll send you the logs. As for operations, we do a put, get a few times and then most likely a remove. We might repeat the put if the info changes. It has a tti of one day. I would guess there would be a few thousand entries. There are a few other caches, but I would think that one is the likely culprit. |
I think I know what the bigger issue is and have a fix lined up. More accurately I've found a real issue and it might be the cause of your bug. Do you have a testing environment we can try a build out in to see if this fixes the issue for you? |
Replied by email, but just to re-iterate: no this issue has only appeared for us on a production platform. We've tried fairly hard to reproduce it elsewhere, with load tests, and general testing and it has also not occurred on different production environments. If you have some pointers as to what might cause it and how we might reproduce then that would be great. I'd really like to be able to do that so we could have some confidence that the issue is fixed and won't happen again. We're a little backed into a corner otherwise as you can imagine. |
We are using clutered ehcache 3.8.1 and after some time ( about 6 hours and under some load )
we see the exception below.
It appears to then lose cache entries.
The exception then repeats roughly every second.
Prior to that there was a single warning - which is also pasted below some 15 mins before the repeating error.
Earlier still there was a single ERROR, again I've pasted this below.
Any suggestions of what the cause might be greatly appreciated.
Repeating error:
Warning:
Single ERROR:
Terracotta is configured with a single off-heap resource:
and the cache being exercised:
The text was updated successfully, but these errors were encountered: