There is no Action mapped for namespace /confluence/plugins/whosediting after confluence update

[Jens Rapp]

Hello,

after upgrading from confluence 6.7 to 6.12 my log files are flooded with messages like these:

2018-12-13 20:58:26,926 ERROR [http-nio-8090-exec-9] [atlassian.confluence.servlet.ConfluenceServletDispatcher] serviceAction There is no Action mapped for namespace /confluence/plugins/whosediting and action name whosediting
 -- referer: http://confluence.local/confluence/pages/viewpage.action?pageId=100270182 | url: /confluence/plugins/whosediting/whosediting.action | traceId: dc5ca1d6f6f24722 | userName: anonymous
2018-12-13 20:58:27,220 ERROR [http-nio-8090-exec-37] [atlassian.confluence.servlet.ConfluenceServletDispatcher] serviceAction There is no Action mapped for namespace /confluence/plugins/whosediting and action name whosediting
 -- referer: http://confluence.local/confluence/pages/viewpage.action?pageId=206799347 | url: /confluence/plugins/whosediting/whosediting.action | traceId: 34e4e45722ad6080 | userName: anonymous
2018-12-13 20:58:27,259 ERROR [http-nio-8090-exec-35] [atlassian.confluence.servlet.ConfluenceServletDispatcher] serviceAction There is no Action mapped for namespace /confluence/plugins/whosediting and action name whosediting
 -- referer: http://confluence.local/confluence/display/0532T21/03+-+Test | url: /confluence/plugins/whosediting/whosediting.action | traceId: c2e98240751aaf2e | userName: anonymous
2018-12-13 20:58:27,798 ERROR [http-nio-8090-exec-45] [atlassian.confluence.servlet.ConfluenceServletDispatcher] serviceAction There is no Action mapped for namespace /confluence/plugins/whosediting and action name whosediting
 -- referer: http://confluence.local/confluence/display/0531T13/KW+44+-2018+WAS+JF | url: /confluence/plugins/whosediting/whosediting.action | traceId: a795b32a3d95376e | userName: anonymous
2

this is very annoying, even if confluence basically works.

I thought there would be synchrony interfering with who's editing but neither deactivating synchrony nor deinstalling whosediting fixed this..

please help.

[Jens Rapp]

just found the problem:

looking at the referer, I found that those urls were wrong, so I looked at the differences between old and recent server.xml.

my root context path was wrong. After changing and restarting, I get no errors anymore.