[AAA-48] MD-SAL Cluster Token Store get stuck reading/writing to the store Created: 14/Jul/15 Updated: 21/Mar/19 Resolved: 08/Feb/16 |
|
| Status: | Resolved |
| Project: | aaa |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Sharon Aicler | Assignee: | Sharon Aicler |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 3991 | ||||||||
| Description |
|
Sometimes when AAA is switch to use the MD-SAL data broker as a cluster token store, during initialization, the read/write transactions get stuck without a timeout. Need to add timeout to the transactions... |
| Comments |
| Comment by Wojciech Dec [ 23/Jul/15 ] |
|
Could you provide more info on the issue? The timeout was intentionally removed as it was causing failures in a cluster environment. |
| Comment by Sharon Aicler [ 23/Jul/15 ] |
|
I a cluster environment, the method "writeClaimAndTokenToStore" is writing the token and registering for a call back. It was observed that sometimes the callback is never executed, hence the code get stuck. After reviewing the code with Moiz, Moiz took the lead and has help me to re-implement this method in a proper cluster aware way so when a timeout is reached, we fail the authentication with a service error. |
| Comment by Sharon Aicler [ 17/Dec/15 ] |
|
I think this bug is identical to 4764... |
| Comment by Ryan Goulding [ 18/Dec/15 ] |
|
That bug appears to be resolved, can we resolve this one as well now? |
| Comment by Ryan Goulding [ 18/Dec/15 ] |
|
Or rather mark as duplicate. |