[OPENIDM-15165] Recon failed with scripted rest with dj sample Created: 17/Jul/20 Updated: 12/Aug/20 Resolved: 12/Aug/20
|Reporter:||Tinghua Xu||Assignee:||Chris Drake|
|Resolution:||Not a defect||Votes:||0|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
IDM master runs on a CentOS 7 machine, Java 11, MySQL as repo
The scripted rest stress test failed to run due to a recon failure(Test was ok on June 20, failed after that) :
IDM log(attached) showed a 401.
To reproduce, run stress test as :
|Comment by Brendan Miller [ 29/Jul/20 ]|
Tinghua Xu What is different between this stress test and the functional test that also tests recon on this sample? (I assume there is one.)
|Comment by Travis Haagen [ 07/Aug/20 ]|
This kind of thing will happen unless you use an explicit table with constraints on the unique fields (e.g., userName).
If you're not using an explicit table, then there is no synchronization of any kind to guarantee that uniqueness constraints will be preserved under high concurrency.
|Comment by Tinghua Xu [ 08/Aug/20 ]|
Brendan Miller, Sorry, missed the request comments earlier. The stress test fails all the time now, from what I can see the stress test import the ldif file attached to DJ before the recon and no other users are created in DJ before the recon, the functional test(recon succeeds) doesn't import the ldif file but does create a user in DJ before the recon. Not sure if the attached ldif file from stress test is still valid or necessary. The recon doesn't involve big count of users.