Activity Stream shows no updated issues, and logs a NoSuchElementException
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
Summary
Symptoms
The activity stream shows there are no recently updated issues, and the following appears in the atlassian-jira.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
2014-03-06 18:40:30,139 StreamsCompletionService::thread-1 ERROR USERNAME 1120x121x5 1vtdrr8 207.67.115.176,127.0.0.1 /plugins/servlet/streams [atlassian.streams.internal.LocalActivityProvider] Exception building feed
java.util.NoSuchElementException
at com.atlassian.streams.api.common.Option$ThrowNoSuchElementException.get(Option.java:56)
at com.atlassian.streams.api.common.Option$3.fold(Option.java:312)
at com.atlassian.streams.api.common.Option.get(Option.java:40)
at com.atlassian.streams.jira.IssueActivityExtractor.extract(IssueActivityExtractor.java:98)
at com.atlassian.streams.jira.JiraStreamsActivityProvider.extractActivity(JiraStreamsActivityProvider.java:152)
at com.atlassian.streams.jira.JiraStreamsActivityProvider.access$100(JiraStreamsActivityProvider.java:48)
at com.atlassian.streams.jira.JiraStreamsActivityProvider$1.call(JiraStreamsActivityProvider.java:101)
at com.atlassian.streams.jira.JiraStreamsActivityProvider$1.call(JiraStreamsActivityProvider.java:94)
at com.atlassian.streams.internal.LocalActivityProvider$FeedFetcher.doInTransaction(LocalActivityProvider.java:205)
at com.atlassian.streams.internal.LocalActivityProvider$FeedFetcher.doInTransaction(LocalActivityProvider.java:186)
at com.atlassian.sal.core.transaction.HostContextTransactionTemplate$1.doInTransaction(HostContextTransactionTemplate.java:25)
at com.atlassian.jira.DefaultHostContextAccessor.doInTransaction(DefaultHostContextAccessor.java:34) <+2>
at java.lang.reflect.Method.invoke(Unknown Source)
...Diagnosis
1
select p.pkey, ji.issuenum from jiraissue ji join project p on (ji.project = p.id) where summary = '';The above SQL detects if there are any issues with an empty summary.
Cause
There is at least one issue with an empty summary, which is tripping up the streams processor. It shouldn't normally be possible to create issues without a summary, though it is possible by a bad plugin.
Solution
Resolution
Go to all of the affected issues and edit the issue, then set the summary to a value
Was this helpful?