com.atlassian.soy.renderer.SoyException: Unable to compile Soy templates at: com.atlassian.servicedesk:agent-view-queue

Atlassian JIRA | Andy Nguyen [Atlassian] | 2 years ago
  1. 0

    h4. +Problem+ Currently installing JIRA Service Desk also installs Atlassian Chaperone. These are interdependent but disabling one won't disable the other altogether. If an admin disables Atlassian Chaperone, accessing a Service Desk will result in an Internal Server Error (500) page with the following stacktrace: {noformat} com.atlassian.soy.renderer.SoyException: Unable to compile Soy templates at: com.atlassian.servicedesk:agent-view-queue com.atlassian.soy.renderer.SoyException: Unable to compile Soy templates at: com.atlassian.servicedesk:agent-view-queue at com.atlassian.soy.impl.DefaultSoyManager.render(DefaultSoyManager.java:124) at com.atlassian.soy.impl.DefaultSoyTemplateRenderer.render(DefaultSoyTemplateRenderer.java:52) at com.atlassian.soy.impl.DefaultSoyTemplateRenderer.render(DefaultSoyTemplateRenderer.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) ... Caused by: com.google.common.util.concurrent.UncheckedExecutionException: java.lang.IllegalStateException: Required plugin module com.atlassian.plugins.atlassian-chaperone:chaperone was either missing or disabled at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2234) at com.google.common.cache.LocalCache.get(LocalCache.java:3970) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3974) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4834) at com.google.common.cache.LocalCache$LocalManualCache.getUnchecked(LocalCache.java:4839) ... {noformat} h4. +Steps to Reproduce+ # Install JIRA Service Desk # Create a new Service Desk # Disable Atlassian Chaperone # Try to access the Service Desk h4. +Workaround+ Do not disable Atlassian Chaperone. If it is disabled, re-enabling it should make the Service Desk accessible again. However, if the plugin is *uninstalled*, then JIRA Service Desk will be disabled and can't be re-enabled. In this case, users can only uninstall JIRA Service Desk and re-install it, which will also re-install Atlassian Chaperone. h4. +Suggestion+ Dependent plugins of JIRA Service Desk should be made unmodifiable and rely on the status of JIRA Service Desk itself.

    Atlassian JIRA | 2 years ago | Andy Nguyen [Atlassian]
    com.atlassian.soy.renderer.SoyException: Unable to compile Soy templates at: com.atlassian.servicedesk:agent-view-queue
  2. 0

    h4. +Problem+ Currently installing JIRA Service Desk also installs Atlassian Chaperone. These are interdependent but disabling one won't disable the other altogether. If an admin disables Atlassian Chaperone, accessing a Service Desk will result in an Internal Server Error (500) page with the following stacktrace: {noformat} com.atlassian.soy.renderer.SoyException: Unable to compile Soy templates at: com.atlassian.servicedesk:agent-view-queue com.atlassian.soy.renderer.SoyException: Unable to compile Soy templates at: com.atlassian.servicedesk:agent-view-queue at com.atlassian.soy.impl.DefaultSoyManager.render(DefaultSoyManager.java:124) at com.atlassian.soy.impl.DefaultSoyTemplateRenderer.render(DefaultSoyTemplateRenderer.java:52) at com.atlassian.soy.impl.DefaultSoyTemplateRenderer.render(DefaultSoyTemplateRenderer.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) ... Caused by: com.google.common.util.concurrent.UncheckedExecutionException: java.lang.IllegalStateException: Required plugin module com.atlassian.plugins.atlassian-chaperone:chaperone was either missing or disabled at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2234) at com.google.common.cache.LocalCache.get(LocalCache.java:3970) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3974) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4834) at com.google.common.cache.LocalCache$LocalManualCache.getUnchecked(LocalCache.java:4839) ... {noformat} h4. +Steps to Reproduce+ # Install JIRA Service Desk # Create a new Service Desk # Disable Atlassian Chaperone # Try to access the Service Desk h4. +Workaround+ Do not disable Atlassian Chaperone. If it is disabled, re-enabling it should make the Service Desk accessible again. However, if the plugin is *uninstalled*, then JIRA Service Desk will be disabled and can't be re-enabled. In this case, users can only uninstall JIRA Service Desk and re-install it, which will also re-install Atlassian Chaperone. h4. +Suggestion+ Dependent plugins of JIRA Service Desk should be made unmodifiable and rely on the status of JIRA Service Desk itself.

    Atlassian JIRA | 2 years ago | Andy Nguyen [Atlassian]
    com.atlassian.soy.renderer.SoyException: Unable to compile Soy templates at: com.atlassian.servicedesk:agent-view-queue
  3. 0

    *Problem Description* Upon starting up Bamboo with Tomcat latest version, the following error will be returned. {noformat} 2014-04-14 22:16:15,472 ERROR [http-bio-8080-exec-7] [BambooFreemarkerManagerSoyHelpers] Error while rendering soy template: navlinks.templates.appswitcher.switcher com.atlassian.soy.renderer.SoyException: Unable to compile Soy template in plugin module: com.atlassian.plugins.atlassian-nav-links-plugin:rotp-menu at com.atlassian.soy.impl.DefaultSoyManager.render(DefaultSoyManager.java:119) at com.atlassian.soy.impl.SoyTemplateRendererImpl.render(SoyTemplateRendererImpl.java:40) at com.atlassian.soy.impl.SoyTemplateRendererImpl.render(SoyTemplateRendererImpl.java:33) ... Caused by: java.lang.IllegalStateException: Required plugin module com.atlassian.plugins.atlassian-nav-links-plugin:rotp-menu was either missing or disabled at com.atlassian.soy.impl.TemplateSetFactory$TemplateSetBuilder.addTemplatesForTree(TemplateSetFactory.java:94) at com.atlassian.soy.impl.TemplateSetFactory$TemplateSetBuilder.access$200(TemplateSetFactory.java:81) ... {noformat} This is not aligned with the [Supported Platform|https://confluence.atlassian.com/display/BAMBOO/Supported+platforms], that specified that it should be compatible with all Tomcat 7. *Steps to replicate* # Download Tomcat 7.0.53 # Point the webapp to Bamboo webapp {code} <Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true"> <Context path="" docBase="../atlassian-bamboo" reloadable="false" useHttpOnly="true"> <!--<Resource name="UserTransaction" auth="Container" type="javax.transaction.UserTransaction"--> <!--factory="org.objectweb.jotm.UserTransactionFactory" jotm.timeout="60"/>--> <Manager pathname=""/> </Context> </Host> {code} # Startup Bamboo and you will get the error

    Atlassian JIRA | 3 years ago | Rian Josua Masikome [Atlassian]
    com.atlassian.soy.renderer.SoyException: Unable to compile Soy template in plugin module: com.atlassian.plugins.atlassian-nav-links-plugin:rotp-menu
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    *Problem Description* Upon starting up Bamboo with Tomcat latest version, the following error will be returned. {noformat} 2014-04-14 22:16:15,472 ERROR [http-bio-8080-exec-7] [BambooFreemarkerManagerSoyHelpers] Error while rendering soy template: navlinks.templates.appswitcher.switcher com.atlassian.soy.renderer.SoyException: Unable to compile Soy template in plugin module: com.atlassian.plugins.atlassian-nav-links-plugin:rotp-menu at com.atlassian.soy.impl.DefaultSoyManager.render(DefaultSoyManager.java:119) at com.atlassian.soy.impl.SoyTemplateRendererImpl.render(SoyTemplateRendererImpl.java:40) at com.atlassian.soy.impl.SoyTemplateRendererImpl.render(SoyTemplateRendererImpl.java:33) ... Caused by: java.lang.IllegalStateException: Required plugin module com.atlassian.plugins.atlassian-nav-links-plugin:rotp-menu was either missing or disabled at com.atlassian.soy.impl.TemplateSetFactory$TemplateSetBuilder.addTemplatesForTree(TemplateSetFactory.java:94) at com.atlassian.soy.impl.TemplateSetFactory$TemplateSetBuilder.access$200(TemplateSetFactory.java:81) ... {noformat} This is not aligned with the [Supported Platform|https://confluence.atlassian.com/display/BAMBOO/Supported+platforms], that specified that it should be compatible with all Tomcat 7. *Steps to replicate* # Download Tomcat 7.0.53 # Point the webapp to Bamboo webapp {code} <Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true"> <Context path="" docBase="../atlassian-bamboo" reloadable="false" useHttpOnly="true"> <!--<Resource name="UserTransaction" auth="Container" type="javax.transaction.UserTransaction"--> <!--factory="org.objectweb.jotm.UserTransactionFactory" jotm.timeout="60"/>--> <Manager pathname=""/> </Context> </Host> {code} # Startup Bamboo and you will get the error

    Atlassian JIRA | 3 years ago | Rian Josua Masikome [Atlassian]
    com.atlassian.soy.renderer.SoyException: Unable to compile Soy template in plugin module: com.atlassian.plugins.atlassian-nav-links-plugin:rotp-menu

    Root Cause Analysis

    1. com.atlassian.soy.renderer.SoyException

      Unable to compile Soy templates at: com.atlassian.servicedesk:agent-view-queue

      at com.atlassian.soy.impl.DefaultSoyManager.render()
    2. com.atlassian.soy
      DefaultSoyTemplateRenderer.render
      1. com.atlassian.soy.impl.DefaultSoyManager.render(DefaultSoyManager.java:124)
      2. com.atlassian.soy.impl.DefaultSoyTemplateRenderer.render(DefaultSoyTemplateRenderer.java:52)
      3. com.atlassian.soy.impl.DefaultSoyTemplateRenderer.render(DefaultSoyTemplateRenderer.java:45)
      3 frames
    3. Java RT
      Method.invoke
      1. sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      2. sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      3. sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      4. java.lang.reflect.Method.invoke(Method.java:606)
      4 frames