Summary
Triggering multiple service provisions via API calls causing some of them to fail randomly.
Question
When customer triggers multiple service provisioning via API call some of the randomly fail to schedule an OO flow and fail with ConcurrentModificationException leading to overall failure of subscription. When parallel subscriptions are running OO typically shows that same flows from different subscriptions are executed at the same time. This functionality is critical for customer as it's part of WW release of new SA services scheduled for October 7th. CSA logs with java exception stack trace are captured and can be provided. CSA version is 4.50 patch 3.
Answer
Workaround Provided:
axis-1.4.1-20160213.152712-313.jar found in attachment of QCIM1D220442
Replace the following and rename the file to reflect the original name “axis-1.4.jar”.
Hotfix planned at upcoming releases of CSA / OO
axis-1.4.1-20160213.152712-313.jar found in attachment of QCIM1D220442
Replace the following and rename the file to reflect the original name “axis-1.4.jar”.
Hotfix planned at upcoming releases of CSA / OO