We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There are a few places in the code where CommCare is pretty sloppy with using static locks.
I just fixed one here: https://github.com/dimagi/commcare-core/pull/645/files#diff-a5c25a223fdbfdb01034706e5380d1c4L29
which was preventing multiple nodeset lookups from happening simultaneously
I think it may be the case that this one:
commcare-core/src/main/java/org/commcare/resources/ResourceManager.java
Line 29 in fe3aca9
Is a huge source of "silent" concurrent locking for formplayer.
The implication of this would be that while using formplayer, only one web request would be able to be manipulating the state of an app at any time.
The text was updated successfully, but these errors were encountered:
dannyroberts
No branches or pull requests
There are a few places in the code where CommCare is pretty sloppy with using static locks.
I just fixed one here:
https://github.com/dimagi/commcare-core/pull/645/files#diff-a5c25a223fdbfdb01034706e5380d1c4L29
which was preventing multiple nodeset lookups from happening simultaneously
I think it may be the case that this one:
commcare-core/src/main/java/org/commcare/resources/ResourceManager.java
Line 29 in fe3aca9
Is a huge source of "silent" concurrent locking for formplayer.
The implication of this would be that while using formplayer, only one web request would be able to be manipulating the state of an app at any time.
The text was updated successfully, but these errors were encountered: