Analytics Client not possible to enable

[Johan Johansson]

I try to migrate JIRA to the cloud, but the JCMA does not start anymore. The error indicates that it reqruies Analytics Client Plugin to be enabled. I have found it's not, but when I press Enable, I get the following error:

ThreadPoolAsyncTaskExecutor::Thread 38 ERROR xxxx 945x521x1 yyyyyy xxx.xxx.xxx.xx /rest/plugins/1.0/com.atlassian.analytics.analytics-client-key [o.e.g.b.e.i.dependencies.st
artup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.atlassian.analytics.client], unsatisfied dependencies: none
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'jiraEventListener' defined in OSGi resource[classpath:com/atlassian/analytics/client/spring/product/Jira
Beans.class|bnd.id=22|bnd.sym=com.atlassian.analytics.client]: Unsatisfied dependency expressed through method 'jiraEventListener' parameter 1; nested exception is org.springframework.beans.factory.Uns
atisfiedDependencyException: Error creating bean with name 'productAnalyticsEventListener' defined in OSGi resource[classpath:com/atlassian/analytics/client/spring/shared/SharedBeans.class|bnd.id=22|bn
d.sym=com.atlassian.analytics.client]: Unsatisfied dependency expressed through method 'productAnalyticsEventListener' parameter 4; nested exception is org.springframework.beans.factory.BeanCreationExc
eption: Error creating bean with name 'log4jAnalyticsLogger' defined in OSGi resource[classpath:com/atlassian/analytics/client/spring/shared/SharedBeans.class|bnd.id=22|bnd.sym=com.atlassian.analytics.
client]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.analytics.client.logger.Log4jAnalyt
icsLogger]: Factory method 'log4jAnalyticsLogger' threw exception; nested exception is java.lang.NullPointerException
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:769)
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:509)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1318)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1158)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:554)

 The JIRA version is pretty old, 8.13.9.

Thankful for any insight!

Best regards

Johan

[Trudy Claspill]

Hello @Johan Johansson 

What version of JCMA are you using?

Can you show us the error message that indicates JCMA can't start because of the Analytics Client?

[Johan Johansson]

Hi thanks for answering, this is the error shown when I load the cloud migration screen.

JCMA version is 1.10.11 so the latest from what I can see. 

2024-01-25 15:34:04,604+0000 https-jsse-nio-8080-exec-20 ERROR jojo 934x127x2 1srec5q 79.136.23.207 /rest/migration/latest/dark-features [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught excep
tion thrown by REST service: service matching filter=[(objectClass=com.atlassian.analytics.api.services.AnalyticsConfigService)] unavailable
org.eclipse.gemini.blueprint.service.ServiceUnavailableException: service matching filter=[(objectClass=com.atlassian.analytics.api.services.AnalyticsConfigService)] unavailable
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceDynamicInterceptor.getTarget(ServiceDynamicInterceptor.java:404)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:136)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:124)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:70)
at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:53)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:136)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:124)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)
at com.sun.proxy.$Proxy4215.canCollectAnalytics(Unknown Source)
at com.atlassian.jira.migration.analytics.MonitoringResourceFilter.isUserNotAgreed(MonitoringResourceFilter.kt:78)
at com.atlassian.jira.migration.analytics.MonitoringResourceFilter.getResponseFilter$lambda$1(MonitoringResourceFilter.kt:48)
... 5 filtered
at com.atlassian.plugins.rest.module.RestDelegatingServletFilter$JerseyOsgiServletContainer.doFilter(RestDelegatingServletFilter.java:160)
... 1 filtered
at com.atlassian.plugins.rest.module.RestDelegatingServletFilter.doFilter(RestDelegatingServletFilter.java:70)
... 32 filtered
at com.atlassian.servicedesk.internal.web.ExternalCustomerLockoutFilter.doFilter(ExternalCustomerLockoutFilter.java:55)
... 8 filtered
at com.atlassian.jira.plugin.mobile.web.filter.MobileAppRequestFilter.doFilter(MobileAppRequestFilter.java:59)
... 4 filtered
at com.atlassian.jira.plugin.mobile.login.MobileLoginSuccessFilter.doFilter(MobileLoginSuccessFilter.java:54)
... 3 filtered
at com.atlassian.diagnostics.internal.platform.monitor.http.HttpRequestMonitoringFilter.doFilter(HttpRequestMonitoringFilter.java:55)
... 3 filtered
at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
... 4 filtered
at com.alphaserve.twofactor.core.services.servlets.impl.FilterServiceImpl.doBeforeDispatchMobileLoginFilter(FilterServiceImpl.java:182)
at com.alphaserve.authplugin.servlets.filters.BeforeDispatchMobileLoginFilter.doFilter(BeforeDispatchMobileLoginFilter.java:26)
... 42 filtered
at com.alphaserve.twofactor.core.services.servlets.impl.FilterServiceImpl.doLoginFilter(FilterServiceImpl.java:128)
at com.alphaserve.twofactor.core.services.servlets.impl.FilterServiceImpl.doLoginFilter(FilterServiceImpl.java:114)
at com.alphaserve.authplugin.servlets.filters.LoginFilter.doFilter(LoginFilter.java:30)
... 3 filtered
at com.atlassian.plugins.slack.analytics.SlackAnalyticsFilter.doFilter(SlackAnalyticsFilter.java:35)
... 3 filtered
at com.atlassian.ratelimiting.internal.filter.RateLimitFilter.doFilter(RateLimitFilter.java:73)
... 3 filtered
at com.atlassian.troubleshooting.thready.filter.AbstractThreadNamingFilter.doFilter(AbstractThreadNamingFilter.java:46)
... 17 filtered
at com.atlassian.jira.security.JiraSecurityFilter.lambda$doFilter$0(JiraSecurityFilter.java:66)
... 1 filtered
at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:64)
... 16 filtered
at com.atlassian.plugins.rest.module.servlet.RestSeraphFilter.doFilter(RestSeraphFilter.java:38)

[Trudy Claspill]

I see the Analytics Client Plugin is one of the System plugins.

Since both it and JCMA are Atlassian products, I think your best course of action is to create an Atlassian support case about this.

https://support.atlassian.com/contact/#/

And it would be great if you report back here what you learn from Atlassian on this problem.