After a PDT warning, I suspect we have a custom code somewhere in E10 that the transaction scope may not be defined and is living a large amount of data on the heap. The PDT did not specify int he results which directive(s) may be causing the issue. There are more than 100 different custom codes written in this E10 environment… is there an easy way I can identify specifically which one it is?
Right now my plan is to trigger each one, one by one, with the trace log on and then take the trace file through the PDT analyzer.
How do you see that it is living in the heap?
PDT warning results stating there is a large amount of data on the heap.
Did you run a config check or what test did you run?
Live memory inspection?
None so far. Just the Epicor PDT. Next I was going to trigger each of our BPMs with custom codes, one by one, and capture the results into a Trace txt file. Then run each trace file through the PDT analyzer. We have more than 100 different custom codes Ill have to do this on… hence why I asked my post about is there another tool that could identify this much faster
I thought that you could take a server trace log and analyze that with the PDT, but I don’t think it breaks out the BPMs one by one.