Investigate and diagnose a strange EJB rollback exception triggered by redetect API

[landreev]

Opening the issue so that the old PR #7631 can be closed (other things that were useful in that PR have been fixed since then; this issue is one thing un-addressed left there).

Triggered by appear to be the keywords. It doesn't look like this really has anything to do with the actual functionality in redetect. The exception appears to be thrown from some innocuous method, like a setting checking. It does not happen on most files. BUT consistently/reproducibly happens on one specific file in prod.:

curl -X POST "http://localhost:8080/api/files/4325124/redetect?key=..."

(and I believe on a few other known files). The above does NOT cause this problem when attempted on a different test server using a copy of the prod. db (!).
We may have seen something similar in other contexts - when checking a setting suddenly causes a problem. This may not be the most pressing issue, but is weird enough to want to figure out what's going on.

See #7631 and #7527 for more info. But the above really describes it. (the only thing I may add later on is an actual stack trace).

[landreev]

This issue has been a candidate for closing quietly for a while.
FWIW, it can no longer be reproduced in prod. as described above. (but, since it was intermittent and unpredictable, it's not at all unlikely that it can still be triggered under some other scenario; still, it doesn't seem to be worth investing any serious amount of effort into investigating this mystery, and there doesn't seem to be any way to figure out what it was quickly, therefore let's just close it).

[cmbz]

2025-01-22: Closing as not planned.