Bugs in logs after App Usage plugin was bundled

XMLWordPrintable

    • 9.16
    • 1
    • Severity 3 - Minor
    • 0

      Issue Summary

      Below exception is reported in the Jira logs after App Usage plugin was bundled.

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Below exception is observed in Jira version 9.17.2.

      Expected Results

      All the App usage plugin modules are enabled and no exceptions are observed.

      Actual Results

      The below exception is thrown in the atlassian-jira.log file:

      2024-12-16 18:07:58,633+0100 web-items-info-map-rebuild-throttle ERROR      [c.atlassian.velocity.DefaultVelocityManager] MethodInvocationException occurred getting message body from Velocity: java.lang.NullPointerException
java.lang.NullPointerException
	at java.base/java.net.URLEncoder.encode(Unknown Source)
	at java.base/java.net.URLEncoder.encode(Unknown Source)
	at com.atlassian.audit.frontend.util.URLEncoderUtil.encode(URLEncoderUtil.java:23)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.base/java.lang.reflect.Method.invoke(Unknown Source)
	at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:385)
...
at com.atlassian.jira.template.velocity.DefaultVelocityTemplatingEngine$DefaultRenderRequest.asPlainText(DefaultVelocityTemplatingEngine.java:94)
	at com.atlassian.jira.plugin.webfragment.JiraWebFragmentHelper.getPlainText(JiraWebFragmentHelper.java:90)
	at com.atlassian.jira.plugin.webfragment.JiraWebFragmentHelper.renderVelocityFragment(JiraWebFragmentHelper.java:84)
	at com.atlassian.plugin.web.model.DefaultWebLink.getRenderedUrl(DefaultWebLink.java:32)
	at com.atlassian.jira.plugin.webfragment.model.JiraWebLink.getRenderedUrl(JiraWebLink.java:58)
	at com.atlassian.app.usage.core.features.user.interaction.servlet.service.WebItemModulesService.getWebItemUrl(WebItemModulesService.kt:131)
	at com.atlassian.app.usage.core.features.user.interaction.servlet.service.WebItemModulesService.maybeMapDescriptorToWebItemInfo(WebItemModulesService.kt:104)
	at com.atlassian.app.usage.core.features.user.interaction.servlet.service.WebItemModulesService.rebuildCache(WebItemModulesService.kt:83)
	at com.atlassian.app.usage.core.features.user.interaction.servlet.service.WebItemModulesService$cacheRebuildScheduler$1.invoke(WebItemModulesService.kt:26)
	at com.atlassian.app.usage.core.features.user.interaction.servlet.service.WebItemModulesService$cacheRebuildScheduler$1.invoke(WebItemModulesService.kt:26)
	at com.atlassian.app.usage.core.modules.CacheRebuildScheduler$scheduleCacheRebuild$$inlined$timerTask$1.run(Timer.kt:149)
	at java.base/java.util.TimerThread.mainLoop(Unknown Source)
	at java.base/java.util.TimerThread.run(Unknown Source)

      Workaround

      Currently there is no known workaround for this behaviour. A workaround will be added here when available. Disabling the plugin helps however is not the recommended solution.

            Assignee:
            Unassigned
            Reporter:
            Yash Singh
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: