JIRA Throws IllegalArgumentException when using 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
When viewing the activity stream gadget in a source outside JIRA (such as Fisheye), JIRA logs the following exception:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
2010-03-22 11:27:56,345 http-8180-Processor21 ERROR whitmore 41276x216x1 ntz3oe /plugins/servlet/streams [atlassian.streams.servlet.StreamsActivityServlet] Error getting activity
java.lang.IllegalArgumentException: The Project argument and its backing generic value must not be null
at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:171)
at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:159)
at sun.reflect.GeneratedMethodAccessor103.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:70)
at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28)
at $Proxy40.hasPermission(Unknown Source)
at sun.reflect.GeneratedMethodAccessor103.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:129)
Cause
Apache Web Proxy is interfering with the project name when configured incorrectly.
Workaround
Remove the Apache Proxy between Fisheye (or the product housing the JIRA activity stream) and JIRA.
Resolution
Atlassian is still investigating the exact configuration that's responsible for this problem. Please comment on this article if you discover any specifics.
Was this helpful?