Skip to content

RTGOV-632 Avoid server side concurrency issue when getting access code#253

Merged
objectiser merged 1 commit intoGovernance:masterfrom
objectiser:RTGOV-632
Dec 11, 2014
Merged

RTGOV-632 Avoid server side concurrency issue when getting access code#253
objectiser merged 1 commit intoGovernance:masterfrom
objectiser:RTGOV-632

Conversation

@objectiser
Copy link
Copy Markdown
Contributor

No description provided.

objectiser added a commit that referenced this pull request Dec 11, 2014
RTGOV-632 Avoid server side concurrency issue when getting access code
@objectiser objectiser merged commit 7905280 into Governance:master Dec 11, 2014
@objectiser objectiser deleted the RTGOV-632 branch December 11, 2014 18:17
@brmeyer
Copy link
Copy Markdown
Member

brmeyer commented Dec 11, 2014

Gary, think this would help S-RAMP? Was this recommended somewhere, or just something you figured out?

@objectiser
Copy link
Copy Markdown
Contributor Author

It may help SRAMP. RTGov appears to be affected by two separate KeyCloak/EAP issues - one related to concurrency, which appears to be fixed by serializing the requests, and the other I am still unsure about. Easiest way to check is whether concurrent requests are being received on the server when the problem occurs for SRAMP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants