So it was really hard trying to understand who is the bustard
We came up with few quick alternatives on how to find it:
- Send mail to all team leaders asking if they know about it (that didn't do any good coz they didn't)
- Iterate on all the source code and searching for "d.xml"
- before we start the processes, create d.xml as readonly and see which process breaks / look at the logs - we used this approach and got the answer in 1 minute
- start reducing processes who run (binary search) - but that will take too much
Any other clever and technical way (that will find the process and the specific plugin if it the one to blame)?
By the way the bustard is me :( (one of my subsystems wrote this debug file dump)