Unable to Edit Activity Stream gadget
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
Symptoms
Users unable to edit any new and existing activity stream gadgets in the dashboard. The following appears in the atlassian-jira.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
2014-08-18 13:19:47,580 http-bio-10443-exec-16 ERROR admin 799x233x1 13nz9z4 10.75.22.97 /rest/activity-stream/1.0/config [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service:
null
java.lang.NullPointerException
at com.atlassian.streams.internal.ProviderFilterOrdering.compare(ProviderFilterOrdering.java:72)
at com.atlassian.streams.internal.ProviderFilterOrdering$1.compare(ProviderFilterOrdering.java:44)
at java.util.TimSort.binarySort(Unknown Source)
at java.util.TimSort.sort(Unknown Source)
at java.util.TimSort.sort(Unknown Source)
at java.util.Arrays.sort(Unknown Source)
at java.util.Collections.sort(Unknown Source)
at com.google.common.collect.Ordering.sortedCopy(Ordering.java:513)
at com.atlassian.streams.internal.ConfigRepresentationBuilder.getConfigRepresentation(ConfigRepresentationBuilder.java:73)
at com.atlassian.streams.internal.rest.resources.StreamsConfigResource.getFilters(StreamsConfigResource.java:39) <+3>
at java.lang.reflect.Method.invoke(Unknown Source) <+18> (DispatchProviderHelper.java:234) (DispatchProviderHelper.java:100) (DefaultMethodInvocation.java:61) (ExpandInterceptor.java:38) (DefaultMethodInv
ocation.java:61) (DispatchProviderHelper.java:132) (DispatchProviderHelper.java:230) (ResourceJavaMethodDispatcher.java:75) (HttpMethodRule.java:288) (ResourceClassRule.java:108) (RightHandPathRule.java:147) (Root
ResourceClassesRule.java:84) (WebApplicationImpl.java:1469) (WebApplicationImpl.java:1400) (WebApplicationImpl.java:1349) (WebApplicationImpl.java:1339) (WebComponent.java:416) (ServletContainer.java:537)
at com.atlassian.plugins.rest.module.RestDelegatingServletFilter$JerseyOsgiServletContainer.doFilter(RestDelegatingServletFilter.java:178) <+1> (ServletContainer.java:795)
at com.atlassian.plugins.rest.module.RestDelegatingServletFilter.doFilter(RestDelegatingServletFilter.java:73) <+16> (DelegatingPluginFilter.java:74) (IteratingFilterChain.java:42)
...
Cause
There are broken application link that the gadget has issue checking the application name.
Resolution
Please try the resolution in your staging environment before work on your production environment.
Backup JIRA
The problematic application link name could be look like "{name}".
Otherwise, remove one application link at a time and see which application link might be causing this problem. It could be a corrupted application link which the application has not been used for some time.
Was this helpful?