If PersonHasTSBAccountDef is deleted and re-created, both processes appear in the Job Queue and block each other (4321148)

If PersonHasTSBAccountDef is deleted and re-created, both processes appear in the Job Queue and block each other

If PersonHasTSBAccountDef is deleted and re-created shortly afterwards, both processes appear simultaneously in the Job Queue and block each other.

This is a product defect (32063).    

WORKAROUND

None.

STATUS

This will be fixed in a future release of the product. If you require this immediately corrected, please contact Support for a hotfix referencing the defect ID 32063.

The processes for deleting/creating accounts may be in the Job Queue at the same time. The scenario is exacerbated when several Account Definitions (AccountDef)that are connected to each other via "required AccountDef".

This makes it possible for insert processes to run before the delete processes.

Furthermore, it can lead to DeadLock situations in the JobQueue, e.g.:

There are two AccountDefs: For ADSAccount and EX0MailBox. The AccountDef for the account is entered as required AccountDef in the mailbox.

In this configuration, when assigning the AccountDefs in the "EX0_PersonHasTSBAccountDef_Autocreate_EX0MailBox/Contact/User" process, an additional job is generated that checks whether the account exists. For this purpose, it is checked whether QBMElementAffectedByJob still contains something for PersonHasTSBAccountDef for the AccountDef of the ADSAccount.

When the AccountDefs are removed, a job is generated in the process "TSB_PersonHasTSBAccountDef_Autodelete_Account" (for the ADSAccount) that checks whether the MailBox has already been removed. To do this, QBMElementAffectedByJob is checked for entries for PersonHasTSBAccountDef for the mailbox's AccountDef.

If the AccountDefs were removed and reassigned promptly, the two waiting jobs of the above processes block each other.