You’re offline. This is a read only version of the page.
Hi all,
I've got MRP running as a batch job on 2 AX partitions. One of them (let's call it Partition A) runs perfectly within 1 hour or so, the other one (let's call it Partition B) within 20 minutes or so on a good day.
Here's the problem: most of the time, the one running on Partition B seems to run forever. If we let it run, it will eventually finish after running for 18 hours and seems like it's looping on the following SQL query:
DECLARE @res int; EXEC @res = SP_GETAPPLOCK @resource = N'ReqPlanVersion:llg:MasterPlan:5637254842', @lockmode = 'update', @locktimeout = -1; SELECT @res;
Running a few minutes trace on the AOS server, it's doing the following in a loop:
In the Session Logs, it seems like it's actually finished doing the job but somehow never releases the lock in SQL.
Processing time:
I do not have extensive knowledge in MRP so still trying to troubleshoot.
Configuration:
AX 2012 R3 CU12
Batch running with 15 helpers accross 2 batch servers.
No deadlock found in SQL during the execution of the job.
Any help would be greatly appreciated.
Thanks and regards,
Kevin
*This post is locked for comments
I have the same question (0)
Update: Been using fewer helpers and didn't change a thing. What seems to have fixed it is modifying the batch group so that it actually runs on only 1 AOS server instead of 2.
Not exactly too sure why but that worked for me.
Cheers.
Kevin
Share
Report
All responses (
Answers (
4
