[MAGNOLIA-2847] User Activation Issue Created: 17/Aug/09  Updated: 23/Jan/13  Resolved: 19/Aug/09

Status: Closed
Project: Magnolia
Component/s: activation
Affects Version/s: 3.6.6
Fix Version/s: 3.6.7, 3.6.8, 4.1.1

Type: Bug Priority: Major
Reporter: Sean McMains Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu, MySQL data store


Issue Links:
Cloners
is cloned by MGNLXAA-20 Activation of non orderable nodes Closed
relation
is related to MAGNOLIA-2713 different ordering of websites in Aut... Closed
is related to MAGNOLIA-2372 Nodes of the type ItemType.FOLDER can... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Since upgrading to 3.6.6 from 3.6.5 a couple of weeks ago, we've been having some problems with activating new users. When we go to activate, the admin console returns an error:

Can't activate: 1 error detected: Message received from subscriber:
child node ordering not supported on node /admin on magnoliaPublic8080

The user has at this point actually been activated, but because of the error, doesn't show as such in the admin console. And contrary to what one might think from the error, the user is displayed correctly in alphabetical order on the public instance as well as the author instance. (The JCR export, however, does show it at the end of the list — it looks like those users aren't kept in order, in spite of what the UI shows.)

Anyway, this isn't a good situation, as our user activation status is displaying incorrect info and giving faulty errors to our support folks who create the accounts.

The trace on our public instance looks like this:

ERROR  info.magnolia.module.exchangesimple.ReceiveFilter ReceiveFilter.java(doFilter:140) 17.08.2009 13:16:16  
child node ordering not supported on node /admin
javax.jcr.UnsupportedRepositoryOperationException: child node ordering not supported on node /admin
    at org.apache.jackrabbit.core.NodeImpl.orderBefore(NodeImpl.java:1723)
    at org.apache.jackrabbit.core.NodeImpl.orderBefore(NodeImpl.java:2030)
    at info.magnolia.cms.core.DefaultContent.orderBefore(DefaultContent.java:704)
    at info.magnolia.module.exchangesimple.ReceiveFilter.orderImportedNode(ReceiveFilter.java:299)
    at info.magnolia.module.exchangetransactional.XAReceiveFilter.update(XAReceiveFilter.java:152)
    at info.magnolia.module.exchangetransactional.XAReceiveFilter.receive(XAReceiveFilter.java:82)
    at info.magnolia.module.exchangesimple.ReceiveFilter.doFilter(ReceiveFilter.java:121)
    at info.magnolia.module.exchangetransactional.XAReceiveFilter.doFilter(XAReceiveFilter.java:59)
    at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:71)
    at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
    at info.magnolia.cms.filters.CosMultipartRequestFilter.doFilter(CosMultipartRequestFilter.java:90)
    at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:71)
    at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
    at info.magnolia.cms.security.BaseSecurityFilter.doFilter(BaseSecurityFilter.java:61)
    at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:71)
    at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
    at info.magnolia.cms.security.LogoutFilter.doFilter(LogoutFilter.java:81)
    at info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAbstractMgnlFilter.java:62)
    at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
    at info.magnolia.cms.security.auth.login.LoginFilter.doFilter(LoginFilter.java:76)
    at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:71)
    at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
    at info.magnolia.enterprise.registration.RegistrationFilter.doFilter(RegistrationFilter.java:50)
    at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:71)
    at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
    at info.magnolia.cms.filters.ContentTypeFilter.doFilter(ContentTypeFilter.java:80)
    at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:71)
    at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
    at info.magnolia.cms.filters.ContextFilter.doFilter(ContextFilter.java:72)
    at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:71)
    at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71)
    at info.magnolia.cms.filters.CompositeFilter.doFilter(CompositeFilter.java:64)
    at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:71)
    at info.magnolia.cms.filters.MgnlMainFilter.doFilter(MgnlMainFilter.java:97)
    at info.magnolia.cms.filters.MgnlMainFilter.doFilter(MgnlMainFilter.java:200)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
    at java.lang.Thread.run(Thread.java:595)


 Comments   
Comment by Jan Haderka [ 17/Aug/09 ]

Seems like maybe something went wrong during the upgrade ... could you please provide export of the /admin folder from the author and from the public (feel free to remove all the users from the exported file, what i'm interested in is just the folder and its metadata)? Thx.

Comment by Sean McMains [ 17/Aug/09 ]

Sure thing! Sent by private email, just to be on the safe side.

Comment by Jan Haderka [ 19/Aug/09 ]

Done on 3.6 branch as of r27284 and on trunk as of 27297.
The issue mentioned doesn't really affect the trunk (4.1.1) as this version uses mgnl:folder instead of nt:folder as a parent, but same thing problem might occur for other types used in custom modules or created in data module.

Generated at Mon Feb 12 03:40:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.