Change Status event : The operation did not complete within the stipulated time.
Exception “The operation did not complete within the stipulated time.”
Set of Rules needs to be validated when change order is moved from pending to submitted status, if validation for all rules is success ,it is then allowed to move to next status else it should remain in Pending status. This is handled by change status event, when the affected items count is more than 70 we are getting error “The operation did not complete within the stipulated time”. and change order is not getting moved to Submitted even if the validation is success.
To handle this we thought of running the validations using separate thread and main thread will return after 10 minutes. After all validation is completed when the child thread moves to next status using changestatus method then the same event is getting triggered and it goes in loop. Is there a way we can achieve this functionality?
Tried increasing trans-timeout-seconds in application ear, but that did not work.
I had this issue before but I’m sure that it can be caused by a bunch of things.
In my case, we were trying to rev an item that had something like 20, 30, 40, 50+ child levels on its BOM. Even though there weren’t any redlines on the ECO (or even MCO), the Agile-Oracle database still updates that BOM with a new Change Id. So as Agile was trying to update the part BOM with the most recent ECO number, our DBA watched as Agile kept trying to get a BOM explosion report via SQL from the database to update. Therefore we eventually fixed it by simplifying the BOM. You may be having something similar due to either the large number of affected items or something weird with one or more of those affected items. Do also run averify just in case there’s any data corruption issues that’s causing issue.
Please also see Doc ID 2214465.1 and Doc ID 2321864.1 on the Oracle website.
Try that. The lovely “the operation did not complete within a stipulated time” is set for 15 minutes in our system. So if something takes longer than 15 minutes to do, Weblogic kills it and rolls the process back.
Thanks Matt,
Issue is not because of BOM, it is because of the event PX which takes more than 15 minutes if the affected items count is aboove 70.
Hi Daniel,
Where did you tried to increase the timeout settings in Application.ear? Is your JTA timeout in Weblogic console set properly? Have you increased timeout in AdminSessionBean? If yes, then it might not work. Because changing status of ECO calls ChangeSessionBean which resides inside pc.jar of application.ear. If you haven’t increased the timeout of ChangeSessionBean, you can try once.
Regards,
Swagoto
