with pdm pro 2016 SP3, is anyone experiencing a situation in which a save of a workflow in the admin tool results in a "hung" admin tool session that then hangs up the entire production pdm system?
My workflow is not particularly large. Also, while I am "building up" the workflow I can successfully save it throughout the day until at some point I experience the hang condition. The effect is limited to just the admin tool for about 20 minutes, then from there all the users start calling me, telling me that pdm pro isn't responding. The moment I kill the admin tool everything comes back to life and the crisis is resolved.
I have attached a picture of the WF. yes, there are a few transitions with the same name, but that is intended, desired, and allowed from what I understand so I'm hoping that isn't the problem...
my sql server has its own dedicated server with 4 cores and 20 GB RAM, so I doubt it is a performance issue, but I could be wrong? I have used sql profiler and while the admin tool is hung I can still see all of the traffic from the other users...
I am running SP3 and do not have a problem saving my workflows. They are from half that workflows size to more than twice as large.
It does sound like you are stuck inside some kind of loop but not sure how that would happen. If you had some conflicting conditions that would only show up when something transitioned through it.
Have you tried to break it down and only save it after adding one state or one transition just to see where it fails? If you created a simple two state transition with nothing special in the transitions does it still fail?