Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A ace
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 36
    • Issues 36
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • adapt
  • ace
  • Merge requests
  • !13

Resolve "Investigate Potential AuditThread Deadlock"

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Michael Ritter requested to merge 61-investigate-auditthread-deadlock into develop Apr 11, 2019
  • Overview 5
  • Commits 49
  • Pipelines 0
  • Changes 23

Closes #61

Testing for IMS Blocking Updates

  • Migration adds new settings if audit.max.block exists (ims.max.retry and ims.reset.timeout)
  • Default values can be loaded if settings do not exist (ims.max.retry and ims.reset.timeout)
  • UI displays new settings (ims.max.retry and ims.reset.timeout)
  • UI updates settings (ims.max.retry and ims.reset.timeout)]
  • AuditThread suspends on failure to communicate with the ims
  • AuditThread can resume if communication to the ims is regained within the retry period
  • AuditThread will fail if the max retry setting is passed
  • AuditTokens can resume
  • AuditTokens can fail
Edited Apr 23, 2019 by Michael Ritter
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: 61-investigate-auditthread-deadlock