Project

General

Profile

Actions

Task #2597

closed

Event: set EXECUTED event result state when task will continue asynchronously (when AcceptedException is returned, e.g. Role recalculation - change type of result code when 2 LRTs run simultaneously)

Added by Ondrej Husník over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Low
Assignee:
Radek Tomiška
Category:
Event
Target version:
Start date:
12/04/2020
Due date:
% Done:

100%

Estimated time:
Owner:

Description

When 2 LRTs, which both recalculate roles, are supposed to be run simultaneously, an error occurs in event audit displaying "task can't be run 2 times". LRTs are rescheduled on background so they run sequentially and behavior is correct though. The error message uses too severe level and causes that result of the IdM status is "FAILED" which distresses customers. Please could you mitigate the level of result code. It could be rather info than error.


Files

BusinessRoleCompositionLRT_cantRun2times.png (301 KB) BusinessRoleCompositionLRT_cantRun2times.png error message Ondrej Husník, 12/04/2020 11:31 AM

Related issues

Related to IdStory Identity Manager - Defect #2524: Adding multiple automatic roles for organizations with many users fails, the second automatic role doesn't existClosedRadek Tomiška10/16/2020

Actions
Related to IdStory Identity Manager - Defect #1538: Business role: Show cyclic role in tree, removing business sub role from business role definition, remove account from sub roleClosedRadek Tomiška03/05/2019

Actions
Actions #1

Updated by Ondrej Husník over 3 years ago

Found in version 10.5.4

Actions #2

Updated by Radek Tomiška over 3 years ago

  • Category set to Event
  • Priority changed from Normal to Low
  • Target version set to 10.7.0
Actions #3

Updated by Radek Tomiška over 3 years ago

  • Status changed from New to In Progress
Actions #4

Updated by Radek Tomiška over 3 years ago

  • Subject changed from Role recalculation - change type of result code when 2 LRTs run simultaneously to Event: set EXECUTED event result state when task will continue asynchronously (when AcceptedException is returned, e.g. Role recalculation - change type of result code when 2 LRTs run simultaneously)
Actions #5

Updated by Radek Tomiška over 3 years ago

  • Related to Defect #2524: Adding multiple automatic roles for organizations with many users fails, the second automatic role doesn't exist added
Actions #6

Updated by Radek Tomiška over 3 years ago

  • Related to Defect #1538: Business role: Show cyclic role in tree, removing business sub role from business role definition, remove account from sub role added
Actions #7

Updated by Radek Tomiška over 3 years ago

  • Status changed from In Progress to Needs feedback
  • Assignee changed from Radek Tomiška to Vít Švanda
  • % Done changed from 0 to 90

I improved common event processing to transform accepted exception to EXECUTED state => event is executed from the event point of view (~ task will be processed asynchronously on background).

Commit:
https://github.com/bcvsolutions/CzechIdMng/commit/494bd8c23a18807989a01781515cdfc4ecbee1c4

Could you provide me a feedback, please?

Note: Cannot be reproduced easy way in develop. UC from dexcription was improved in #1538 (10.6.0) and in #2529 (new @IdmCheckConcurrentExecution annotation was introduced).

Actions #8

Updated by Vít Švanda over 3 years ago

  • Status changed from Needs feedback to Resolved
  • % Done changed from 90 to 100

I did review. Thanks for this improvement.

Actions #9

Updated by Vít Švanda over 3 years ago

  • Assignee changed from Vít Švanda to Radek Tomiška
Actions #10

Updated by Radek Tomiška over 3 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF