Failed to obtain client registration lock, cannot update potential client message seen after startup
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
要約
After first starting Confluence, a "Failed to obtain client registration lock, cannot update potential client" message is observed in atlassian-confluence.log
環境
7.4.0
診断
The following will be seeing in atlassian-confluence.log:
020-06-26 17:25:45,124 INFO [Catalina-utility-1] [com.atlassian.confluence.lifecycle] init Confluence is ready to serve
2020-06-26 17:26:00,446 ERROR [http-nio-8090-exec-2] [mywork.host.rest.ExceptionLogger] toResponse Exception thrown from REST resource
-- url: /rest/mywork/1/client | traceId: f08081e11ef49611 | userName: anonymous
java.lang.IllegalStateException: Failed to obtain client registration lock, cannot update potential client 35b45543-5488-3a1f-xxxxxxxxx
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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:192)
at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$1.intercept(DispatchProviderHelper.java:83)
at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:53)
at com.atlassian.plugins.rest.common.expand.interceptor.ExpandInterceptor.intercept(ExpandInterceptor.java:42)
at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:53)
at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper.invokeMethodWithInterceptors(DispatchProviderHelper.java:110)
at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker._dispatch(DispatchProviderHelper.java:190)
at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)原因
If this message only shows up once after startup then it can be safely disregarded, the MyWork module (Notifications) has not fully stated yet when the message is logged. Once it fully initializes the message does not repeat.