Communication breakdown when clicking on the tab to attempt to link a Confluence page
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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.
*Except Fisheye and Crucible
Problem
On an existing issue, click on More > Link > Confluence page and users will be getting the Communication breakdown error.
The following appears in the atlassian-jira.log
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
2018-02-22 16:43:02,269 http-nio-8080-exec-22 ERROR vcr 1133x10539x2 u6la1n 0:0:0:0:0:0:0:1 /secure/LinkConfluencePage!default.jspa [c.a.j.web.dispatcher.JiraWebworkActionDispatcher] Exception thrown from action 'LinkConfluencePage!default', returning 404
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.atlassian.jira.plugin.link.confluence.LinkConfluencePage': Unsatisfied dependency expressed through constructor argument with index 10 of type [com.atlassian.jira.plugin.link.confluence.ConfluenceApplicationLinks]: No qualifying bean of type [com.atlassian.jira.plugin.link.confluence.ConfluenceApplicationLinks] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {}; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type [com.atlassian.jira.plugin.link.confluence.ConfluenceApplicationLinks] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {}
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:749)
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:185)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1143)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1046)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:510)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:342)
...
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type [com.atlassian.jira.plugin.link.confluence.ConfluenceApplicationLinks] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {}
at org.springframework.beans.factory.support.DefaultListableBeanFactory.raiseNoSuchBeanDefinitionException(DefaultListableBeanFactory.java:1373)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1119)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1014)
at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:813)
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:741)Diagnosis
Reproduce the issue in JIRA safe mode. If the issue cannot be reproduced in JIRA safe mode, identify the offending add-on/plugin by disabling one at a time and reproduce the issue.
Workaround
Disable the offending add-on/plugin to ensure that the linking feature works fine while checking with the add-on/plugin vendor on the issue.
Was this helpful?