-
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 Loading...
- relates to
-