as these users are reporting:
apparently the MasIndexer in Hibernate Search triggers this log, but I
don't actually want it to lock I just want to re-attach objects to the
Session so I'm using Lock.NONE.
I'm not familiar with this, could someome tell if we should
a) lower the log severity in ORM
b) fix something we're not doing properly in Search
c) maybe make sure we log it only once?
d) add a filthy looking Lock.NONE_AND_QUIET :-P