LockLocalServiceImpl locking retry mechanism isn't clear in logs

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.0.X, 7.1.X, 7.2.X, 7.3.X, Master
• Fix Version/s: 7.0.0 DXP FP100, 7.0.X, 7.1.10 DXP FP23, 7.1.10.6 SP6, 7.1.X, 7.2.10 DXP FP12, 7.2.X, 7.3.7 CE GA8, 7.3.10 DXP FP2, 7.3.X, 7.4.0 CE GA1, 7.4.13 DXP GA1, Master
• Component/s: Core Infrastructure
• Labels:
  • ee-ts
  • liferay-dxp-71-sp6
  • liferay-fixpack-de-100-7010
  • liferay-fixpack-dxp-12-7210
  • liferay-fixpack-dxp-2-7310
  • liferay-fixpack-dxp-23-7110
• Branch Version/s:
  7.3.x, 7.2.x, 7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Git Pull Request: https://github.com/shuyangzhou/liferay-portal/pull/9856

When dealing with a race condition regading the use of the locking mechanism we have an eternal retry in order to create the lock, but if a couple of threads perform the update simultaneously, although the logic works, the following error can be traced in the logs:

2021-03-16 16:48:15.956 ERROR [liferay/background_task-2][JDBCExceptionReporter:234] Duplicate entry 'com.liferay.portal.kernel.backgroundtask.BackgroundTaskExecutor-' for key 'IX_228562AD'

This can generate confusion in order to understand if it's a real error or if it has been handled by Liferay's code.