[atlassian.streams.internal.LocalActivityProvider] Error building feed due to java.lang.NullPointerException
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
After the upgrade of JIRA, you are not able to see any issues in the instance:
The following appears in the atlassian-jira.log:
1
2
3
4
5
2013-08-02 09:19:18,846 StreamsCompletionService::thread-43 ERROR ahmad.danial 559x373x1 1xpf0pl 10.7.66.24 /rest/activity-stream/1.0/config [atlassian.streams.internal.LocalActivityProvider] Error building feed
java.lang.NullPointerException
at com.atlassian.jira.issue.search.parameters.lucene.DefaultPermissionQueryFactory.collectProjectTerms(DefaultPermissionQueryFactory.java:170)
at com.atlassian.jira.issue.search.parameters.lucene.DefaultPermissionQueryFactory.getQuery(DefaultPermissionQueryFactory.java:68)
...
Also, there can also be a possibility that an ERROR stack trace related to JIRA Agile will appear on the log as well:
1
2
3
4
5
2013-08-02 09:19:18,700 http-bio-8080-exec-9 ERROR ahmad.danial 559x375x3 1xpf0pl 10.7.66.24 /rest/greenhopper/1.0/progress-bar-stats/generate [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service
java.lang.NullPointerException
at com.atlassian.jira.issue.search.parameters.lucene.DefaultPermissionQueryFactory.collectProjectTerms(DefaultPermissionQueryFactory.java:170)
at com.atlassian.jira.issue.search.parameters.lucene.DefaultPermissionQueryFactory.getQuery(DefaultPermissionQueryFactory.java:68)
...Cause
The cause is unknown.
Workaround
Run the Database Integrity Checker to ensure that all JIRA data is in a consistent state. Fix all the ERRORs (if there are any).
Reindex JIRA instance
Restart JIRA instance
If the above doesn't work, please try to restore the last backup that you have and perform the JIRA upgrade again. The problem should not be present anymore after that.
Was this helpful?