-
Type:
Bug
-
Resolution: Incomplete
-
Priority:
Low
-
None
-
Affects Version/s: 7.4.13
-
Component/s: Core - Workbox
-
None
-
1
-
Severity 3 - Minor
Issue Summary
The tack trace Failed to obtain client registration lock floods Confluence
Steps to Reproduce
Unknown
Expected Results
No errors
Actual Results
2021-10-08 09:11:15,058 ERROR [http-nio-8090-exec-1] [mywork.host.rest.ExceptionLogger] toResponse Exception thrown from REST resource -- url: /rest/mywork/1/client | traceId: xxxx | userName: anonymous java.lang.IllegalStateException: Failed to obtain client registration lock, cannot update potential client xxxxxx at com.atlassian.mywork.host.service.ClientServiceImpl.updatePotentialClient(ClientServiceImpl.java:362) at com.atlassian.mywork.host.service.ClientServiceImpl.updatePotentialClient(ClientServiceImpl.java:310) at com.atlassian.mywork.host.rest.ClientResource.clientRegistration(ClientResource.java:50) at jdk.internal.reflect.GeneratedMethodAccessor3047.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source)
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available