-
Bug
-
Resolution: Fixed
-
Medium
-
6.6.0, 6.6.1, 6.6.8, 6.7.2, 6.9.0, 6.12.2, 6.14.1, 6.13.8
-
25
-
Severity 3 - Minor
-
91
-
Summary
Workbox Notification does not work and shows empty page on first attempt following a Confluence restart. It will work and able to retrieve information on the next attempts/ page refresh.
Steps to Reproduce
- On a fresh installation of Confluence,
- Click on the Workbox Notification icon on the top right corner
Expected Results
The workbox notification loads correctly
Actual Results
- The workbox notification shows blank page:
- After a while, at times, a System Error appears in the page after a page refresh
The following appears in the atlassian-confluence.log when the page is blank
2018-03-07 23:20:57,928 ERROR [http-nio-8090-exec-5] [atlassian.confluence.event.ConfluenceEventDispatcher] run There was an exception thrown trying to dispatch event [com.atlassian.mywork.host.event.BeforeCountNewNotificationsEvent@31bba1bf] from the invoker [com.atlassian.confluence.event.ConfluenceListenerHandlersConfiguration$TimingListenerHandler$1$1@7794c789]
-- referer: http://localhost:8090/dashboard.action | url: /rest/mywork/latest/status/notification/count | traceId: 2877b0225ae534da | userName: admin
java.lang.RuntimeException: service proxy has been destroyed. Listener: com.atlassian.mywork.host.service.ClientServiceImpl event: com.atlassian.mywork.host.event.BeforeCountNewNotificationsEvent
Eventually, it will timeout with the following:
2018-03-07 23:22:44,209 ERROR [http-nio-8090-exec-5] [[Standalone].[localhost].[/].[servlet-module-container-servlet]] log Servlet.service() for servlet [servlet-module-container-servlet] in context with path [] threw exception
java.lang.RuntimeException: java.util.concurrent.TimeoutException
at com.google.common.base.Throwables.propagate(Throwables.java:160)
The following appears in the log when seeing the System Error:
2018-03-08 18:43:05,452 ERROR [http-nio-8090-exec-6] [host.util.concurrent.LockedTaskExecutor] executeUnderLock Timed out waiting for lock before getting last modified date -- referer: http://localhost:8090/dashboard.action | url: /plugins/servlet/notifications-miniview | traceId: 56ebeb370dca72ad | userName: admin java.util.concurrent.TimeoutException at com.atlassian.mywork.host.util.concurrent.LockedTaskExecutor.tryExecuteUnderLock(LockedTaskExecutor.java:66) at com.atlassian.mywork.host.util.concurrent.LockedTaskExecutor.executeUnderLock(LockedTaskExecutor.java:116) at com.atlassian.mywork.host.service.LocalRegistrationServiceImpl.getLastModified(LocalRegistrationServiceImpl.java:205) at com.atlassian.mywork.host.service.LocalRegistrationServiceImpl.getCacheValue(LocalRegistrationServiceImpl.java:244) at com.atlassian.mywork.host.servlet.ServletRenderer.renderWithAnchor(ServletRenderer.java:79) at com.atlassian.mywork.host.servlet.ServletRenderer.renderWithAnchor(ServletRenderer.java:46) at com.atlassian.mywork.host.servlet.NotificationsMiniviewServlet.doGet(NotificationsMiniviewServlet.java:23)
Workaround
Refresh the page a couple of times
Notes
The issue happens to every user, during the first time accessing Workbox Notification following a restart.
Other than restarting Confluence, this can be easily replicable by accessing Workbox Notification for the first time following enabling a previously disabled Workbox plugins::
- Workbox - Common Plugin
- Workbox - Confluence Provider Plugin
- Workbox - Host Plugin
- has a regression in
-
-
- Closed
-
- mentioned in
-
Page Failed to load
- relates to
-
PSR-272
You do not have permission to view this issue
[CONFSERVER-55134] Workbox Notification will timeout on first attempt, and shows blank page and System Error message
still have this issue after upgrade 7.1 to 7.4. help next
look at manage add-ons then system addons. search for workbox and you should be able to see an system addon disabled. enable that and wait a bit, I believe the plugins timeout may be too short for this system addon to enable
+1 for this to be ported to currently supported Enterprise Versions (6.6 and 6.13) - we are still on 6.6 and when we finally are able to update to 6.13 next quarter, we will not be leaving it until the latter half of 2020...
I agree with @SteveWolf - It process for backporting to supported Enterprise Versions (6.6.x and 6.13.x) seems unclear and the Bugs close out with the initial release and do not include the backporting. Can you confirm if this will be heading to 6.6 and 6.13 as new bugfix versions?
Steve Wolfe
added a comment - I would have thought you would have backported this to 6.13.r A fix for this issue is available to Server and Data Center customers in Confluence 6.15.2.
Upgrade now or check out the Confluence 6.15 Release Notes to see what other issues are resolved.
Merle Fischer
added a comment - Okay, we are seeing this issue in a little bit of a different way in a client's system just upgraded from 5.10. to 6.13.3., Notification Box shows that there are no notifications yet - even though therer clearly should be notifications from the past. Creating new notificaitons by mentioning someone does not generate any notifications in the workbox.
Workaround of reload does not work, Notification box stays empty. I did see the above mentioend stackm trace once or twice right after restart of CONF.
Update to 6.15.2 is not an option for us, as client wants to stay on ER.
Could you let me know when there will be a fix for this in the ER version and whether I need to file a new Bug ticket for this?
Thanks
Merle Fischer
added a comment - Okay, we are seeing this issue in a little bit of a different way in a client's system just upgraded from 5.10. to 6.13.3., Notification Box shows that there are no notifications yet - even though therer clearly should be notifications from the past. Creating new notificaitons by mentioning someone does not generate any notifications in the workbox.
Workaround of reload does not work, Notification box stays empty. I did see the above mentioend stackm trace once or twice right after restart of CONF.
Update to 6.15.2 is not an option for us, as client wants to stay on ER.
Could you let me know when there will be a fix for this in the ER version and whether I need to file a new Bug ticket for this?
Thanks
Same problem with 7.2.1. Thanks for the tipps, deyura. This helps.