-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
HTTPServerLoadTest can get stuck #13
Comments
I guess this could be fixed by using this code in
|
Hm, seems sensible to me. Did you try it? |
I cannot reproduce the bug, so there's not much I can try (except running the tests and that works). |
Urg, that sure is a problem. The UnifierConfiguration was supposed to be I think we should use a ConcurrentHashMap for now, because at least btw, I guess it's a good time to share my thoughts on how I wanted to On Tue, Oct 1, 2013 at 8:55 PM, Daniel Naber notifications@github.comwrote:
|
I just committed a fix that seems to work. Well, I could reproduce the problem a few times with the FrenchConcurrencyTest. The HashMaps has been replaced by ConcurrentHashMaps and the ArrayList stored as value in the equivalenceFeatures has been replaced by a CopyOnWriteArrayList. The later change is 'just in case'. I was not able to reproduce the bug in the HTTPServerLoadTest, so I'm keen to see if you can still reproduce the bug. |
I could never reproduce it, it only happened once (but I didn't try running the test for hours...). Could you please document your fix in CHANGES.txt? |
Done. |
I'll close this issue as it should've been fixed now. Issue #14 might change something on this fix, hopefully the removal of the concurrent collections that were implemented as workaround. |
It happened to me once that the test got stuck with 200% CPU load. The stacktrace was this (quoting only the part that matters):
The text was updated successfully, but these errors were encountered: