The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Confluence Notifications never load

CA Operations
June 6, 2016

We have a migrated COnfluence 6.0 installation (Was on cloud, now local).  One of our users is reporting that Confluence Notifications never load for her.  In the error log, we see

2016-06-06 11:17:08,146 ERROR [http-nio-8091-exec-8] [mywork.host.rest.ExceptionLogger] toResponse Exception thrown from resource
– referer: https://confluence.REDACTEDcom/plugins/servlet/notifications-miniview | url: /rest/mywork/latest/notification/nested | traceId: d71438658d5e6f39 | userName: USERNAME
java.lang.NullPointerException
at com.atlassian.mywork.host.service.AppLinkHelper.stripBaseUrl(AppLinkHelper.java:129)

 

This ticket ( https://confluence.atlassian.com/confkb/notifications-spin-loading-forever-in-the-workbox-and-never-complete-365003046.html ) says "there is corruption in the database" and the answer is to remove all the notifications for all the users.  This seems awfully heavy handed, particularly when we have several hundred users.  Is there a way to repair the notifications (or purge them) just for one user?

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Abhijit Das
October 17, 2016

Getting the same issue in 5.9.12 How did you resolve it?

0 votes
Steven F Behnke
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
June 9, 2016

My initial thought would be to duplicate your instance to a test server and then try the workaround. If that fixes your issue, I would follow up with Support and try to find a more reasonable workaround. 

TAGS
AUG Leaders

Atlassian Community Events