-
Task
-
Resolution: Unresolved
-
Minor
-
None
-
5.0.1
-
None
Some warning messages in, say, LockManager for when lock conflicts occur should probably be reassigned as info, since we a) always fail safe, and b) return a status that indicates a lock conflict has happened.
Hasn't been much of an issue to date, but the increase of multicore and Vert.x use could show these up a lot more.
- is related to
-
JBTM-2593 Suggest making this read_state INFO not WARN
- Closed