I have an application with 2 user roles. Both user roles have custom home pages that display a list of an entity - BillingSheet - with different Xpath constraints. Earlier this week, I upgraded to Modeler 4.6, not sure if this is related or not. When I login as role A, everything works, no problem. When I login with role b - I receive an error message - unexpected error with the following stack trace: 2013-09-27 05:34:28.502 ERROR - Connector: An error has occurred while handling the request. [User 'ASJHHospitalSupport' with session id '45fc3dd0-052b-40f6-9468-a153ce71923b' and roles 'HospitalGatekeeper'] 2013-09-27 05:34:28.502 ERROR - Connector: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"amount":20,"sort":[{"direction":{},"memberName":"DateOfSurgery"}],"formName":"BillingSheet.BillingSheet_List_HospitalAccount","returnsCount":true,"offset":0,"type":"RetrieveXPathSchemaRawAction","xpath":"//BillingSheet.BillingSheet[BillingSheet.BillingSheet_CurrentBillingSheetStatus/BillingSheet.BillingSheetStatus/Sequence = 10]"}', all database changes executed by this action were rolled back at com.mendix.core.actionmanagement.CoreAction.c(SourceFile:515) Caused by: l: An exception has occurred for the following request(s): fw (depth = -1, amount = 20): //BillingSheet.BillingSheet[BillingSheet.BillingSheet_CurrentBillingSheetStatus/BillingSheet.BillingSheetStatus/Sequence = 10] at x.a(SourceFile:49) Caused by: l: Exception occurred while retrieving data. (SQL State: 42601, Error Code: 0) at H.a(SourceFile:1398) Caused by: org.postgresql.util.PSQLException: ERROR: subquery has too many columns Position: 1101 at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2101) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1834) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:510) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:386) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:271) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at H.a(SourceFile:313) at H.a(SourceFile:209) at H.a(SourceFile:159) at H.a(SourceFile:148) at z.a(SourceFile:41) at dA.a(SourceFile:192) at dA.a(SourceFile:150) at dA.a(SourceFile:83) at dE.a(SourceFile:68) at x.a(SourceFile:43) at h.a(SourceFile:269) at hA.a(SourceFile:118) at hA.a(SourceFile:89) at hA.executeAction(SourceFile:28) at com.mendix.systemwideinterfaces.core.UserAction.execute(SourceFile:57) at com.mendix.core.actionmanagement.CoreAction.call(SourceFile:457) at gH.execute(SourceFile:315) at jf.a(SourceFile:321) at com.mendix.externalinterface.connector.RequestDispatching$Worker.a(SourceFile:170) at com.mendix.externalinterface.connector.RequestDispatching$Worker$a.a(SourceFile:161) at com.mendix.externalinterface.connector.RequestDispatching$Worker$a.apply(SourceFile:160) at akka.actor.Actor$class.apply(Actor.scala:545) at com.mendix.externalinterface.connector.RequestDispatching$Worker.apply(SourceFile:156) at akka.actor.LocalActorRef.invoke(ActorRef.scala:910) at akka.dispatch.MessageInvocation.invoke(MessageHandling.scala:25) at akka.dispatch.ExecutableMailbox$class.processMailbox(ExecutorBasedEventDrivenDispatcher.scala:223) at akka.dispatch.ExecutorBasedEventDrivenDispatcher$$anon$4.processMailbox(ExecutorBasedEventDrivenDispatcher.scala:123) at akka.dispatch.ExecutableMailbox$class.run(ExecutorBasedEventDrivenDispatcher.scala:195) at akka.dispatch.ExecutorBasedEventDrivenDispatcher$$anon$4.run(ExecutorBasedEventDrivenDispatcher.scala:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) at akka.dispatch.MonitorableThread.run(ThreadPoolBuilder.scala:192) Any insight about what might be happening?
asked
Mike Kumpf
1 answers
2
This problem has been resolved.
We traced the issue to an access rule on the entity.
Deleting the access rule eliminated the problem.
Adding the access rule to the entity again did not cause the problem to occur.
So it seems that there was something buggy about the access rule processing that surfaced when we upgraded to 4.6 - whatever it was that was causing this was eliminated by deleting and re-adding the access rule.