Hi Magnolians,
We have another strange effect in Production that I need some support with:
For certain specific content we have problems with activation. It's DMS
content, but not particularily large. The problem seems to occur when
activating with sub-nodes, and not when activating affected nodes directly.
The error is reported as:
info.magnolia.cms.exchange.ExchangeException: Message received from
subscriber: User not allowed to Read path [/bka-
fotoservice/Neueste-Bilder/Bild0053]
on the author instance, and:
info.magnolia.cms.security.AccessDeniedException: User not allowed to Read
path [/bka-fotoservice/Neueste-Bilder/Bild0053]
on the public instance.
Of course, the user actually has the rights to edit the content in question,
both on author and on public.
So what's going on?
Some debugging (stack traces are at the end of this email) show that the error
occurs in info.magnolia.module.exchangetransactional.CopyUtil.clone(), when the
public System is reading/writing content from the mgnlSystem workspace.
To further investigate, I connected to the mgnlSystem workspace with a JCR
Browser. I found all kinds of content in the mgnlSystem workspace, including
several copies of the "problem content" in different levels of the hierarchy.
So, as a test (don't worry, not in production) I simply deleted any content in
mgnlSystem that looked like it might have come from our DMS. After deleting
that content, the activation worked without any errors. Ergo: the activation
problems were caused by the content in mgnlSystem.
The first Question I have is: what *should* be the contents of "mgnlSystem"?
If this workspace is used only as temporary storage, should it not be empty of
content, except while an activation is in progress?
2nd Question:
I'm not really able to follow the activation code, since I am unsure of the
requirements that motivate the use of mgnlSystem etc... It's all quite
complicated! So, what can be the implications of existing content in mgnlSystem
on the activation process?
3rd Question:
Can I delete the content of the mgnlSystem workspace in production safely?
If no, how do I solve this problem in production?
If yes, can I simply delete the workspace folder for mgnlSystem (since I can't
use the JCR Browser tool in production)?
Finally, the important question:
How can I prevent this issue from occurring in the future?
Might it be a good idea to clear out the mgnlSystem workspace when magnolia
starts (since an activation task can't survive a tomcat reboot anyway)?
Thanks a lot for any advice on this!
Regards from Vienna,
Richard
PS: Find attached a stack-trace of the error from the public node:
ERROR info.magnolia.module.exchangesimple.ReceiveFilter 27.02.2012 14:55:28 --
User not allowed to Read path [/bka-fotoservice/Neueste-Bilder/Bild0053]
info.magnolia.cms.security.AccessDeniedException: User not allowed to Read path
[/bka-fotoservice/Neueste-Bilder/Bild0053]
at info.magnolia.cms.core.Access.isGranted(Access.java:64)
at
info.magnolia.cms.core.DefaultContent.<init>(DefaultContent.java:133)
at
info.magnolia.cms.core.DefaultHierarchyManager.getContentByUUID(DefaultHierarchyManager.java:470)
at
info.magnolia.module.exchangetransactional.CopyUtil.clone(CopyUtil.java:196)
at
info.magnolia.module.exchangetransactional.CopyUtil.copyToSystem(CopyUtil.java:247)
at
info.magnolia.module.exchangetransactional.XAReceiveFilter.update(XAReceiveFilter.java:138)
at
info.magnolia.module.exchangetransactional.XAReceiveFilter.receive(XAReceiveFilter.java:84)
at
info.magnolia.module.exchangesimple.ReceiveFilter.doFilter(ReceiveFilter.java:136)
at
info.magnolia.module.exchangetransactional.XAReceiveFilter.doFilter(XAReceiveFilter.java:61)
at
info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:88)
at
info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:82)
at
info.magnolia.cms.security.BaseSecurityFilter.doFilter(BaseSecurityFilter.java:64)
at
info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:88)
at
info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:82)
etc...
----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
