Structure Gadget Macro Fails to Load on Confluence Page

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.



Attempting to insert a Structure Gadget into a Confluence page results in an internal server error and failure to render the macro successfully.


Confluence integrated with Jira


The following stack trace will appear in the logs when attempting to add the Structure Gadget to a Confluence page. 

2020-01-17 02:58:41,874 https-jsse-nio-8443-exec-62 url:/rest/structure/2.0/value username:admi ERROR AE06290 178x6727045x1 admin /rest/structure/2.0/value [] [Structure REST API] error when calling POST /value ?={"jobId":null,"requests":[{"forestSpec":{"structureId":81211,"version":null,"...
com.almworks.jira.structure.api.error.StructureRuntimeException: com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.almworks.jira.structure]
	at com.almworks.structure.commons.platform.ClusterSyncToolsFactory$AtlassianCacheAdapter.get(
	at com.almworks.structure.commons.platform.LazilyCreatedCache.get(
	at com.almworks.jira.structure.structure.AOBasedStructureManager.getStructureBeanOrNull(
	at com.almworks.jira.structure.structure.AOBasedStructureManager.getStructurePermission(

Conversely, the following stack trace may be seen from the Jira logs indicating problems loading plugin code from ActiveObjects bundle Jira Structure: 

2020-01-23 00:48:21,643 https-jsse-nio-8443-exec-48 WARN admin 48x7570858x1 1g77v0l / [c.atlassian.ozymandias.SafePluginPointAccess] Unable to run plugin code because of 'com.almworks.jira.structure.api.error.StructureRuntimeException - com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.almworks.jira.structure]'


This problem can be caused by corrupted plugin cache on the Jira side. When this happens, the system may not be able to render the Structure Gadget plugin code as expected and the failure is seen on the front end. 


Restart the affected Jira node and retest the behavior. 

Last modified on Feb 4, 2020

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.