My dashboard show the results of several filters. At the bottom of each section (filter) there is the total number of issues selected by the filter. Clicking on that total normally shows the Search for Issues page with the filter and the results. However, now, if the filter results are more than 20 then clicking on that total gives a 500 error with the message
com.atlassian.jira.util.dbc.Assertions$NullArgumentException: stringValue should not be null!
On the dashboard the filter selection will display the first 10 items from the filter and I can scroll to the second and third pages (thus showing all issues selected by the filter) without any problem. I can also select the filter on the Search for Issues page and the results are shown without any problems.
We are using version 7.3.6 build 73017.
I have a PDF with all the error messages (288kb) and a support zip (200mb) if that is any help.
Thanks for any insight in to resolving this issue you can give.
Could you have a look at the log file again and let us know any ones that you see when the issue occurs that starts with "ERROR" as well as the "Caused by" line at the bottom? This will help us to narrow down the issue.
Could you also let us know if this occurs on every dashboard, or only specific ones?
Are other users able to replicate the problem?
Sorry for taking so long to reply. The log appears to be filled with "Broken Pipe" error messages. This is the last one:
Error serving file for path /84210/84210_image-2017-09-25-16-04-01-821.png: com.atlassian.jira.exception.DataAccessException: org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe
com.atlassian.jira.issue.attachment.AttachmentReadException: com.atlassian.jira.exception.DataAccessException: org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe
Caused by: com.atlassian.jira.exception.DataAccessException: org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe
Caused by: org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe
... 9 more
Caused by: java.io.IOException: Broken pipe
at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
... 10 filtered
... 19 more
2017-12-07 13:35:26,631 http-nio-127.0.0.1-8080-exec-75
Thank you! It looks like a similar bug has been raised with the same error, but not the same cause, so I'd like to raise a support ticket so we can have a look at the support zip and further.
Please have a look at your email for my response.
Once the issue is resolved please feel free to share the answer here so it can help future users.
Could you please share with me the error messages as I asked from Andrew earlier? You can check the Jira Server Application Logs, and when you trigger the error, look for anything that starts with ERROR and ends with "Caused by:" and then we can know exactly what is causing the problem.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs