Hi guys, We're having a strange issue with a query rule on one of

caz

A Score Level 1

over 9 years ago

Hi guys,

We're having a strange issue with a query rule on one of our sites. We're seeing 'Error evaluating function 'queryruleexec' : Unexpected error executing query' in the front-end and this in the logs:

14:33:26,501 INFO [stdout] (ajp-/0.0.0.0:8009-36) 2015-05-27 14:33:26,499 [ajp-/0.0.0.0:8009-36] ERROR com.appiancorp.suiteapi.content.ContentAccess - An error occurred while trying to test the rule: [Content:id=null,name=tyutyu,type=32,subtype=1,visibility=35,security=143,attributes={dep_functions=[Ljava.lang.String;@691f04b6, dep_rules=[Ljava.lang.Long;@736e7ea4, definition=#"84b9b493-3954-4456-8f78-9376bf6ec92d"("Enable Therapy Services", "Moving Minds")
14:33:26,501 INFO [stdout] (ajp-/0.0.0.0:8009-36)
14:33:26,501 INFO [stdout] (ajp-/0.0.0.0:8009-36) , dep_types=[Ljava.lang.String;@5b3c7c30, dep_variables=[[Ljava.lang.String;@5ffd621b}]
14:33:26,501 INFO [stdout] (ajp-/0.0.0.0:8009-36) com.appiancorp.process.expression.E...

Discussion posts and replies are publicly visible

Parents

0 srikanthm0004
A Score Level 1
over 6 years ago

Has anyone found the solution for this error : APNX-1-4164-028?

We are getting the same error and we cross checked the view to make sure there isn't any invalid date formats.

21:35:14,295 INFO [stdout] (Appian Work Item - 59831 - execution01 : ExpressionGroupRequest) Caused by: com.appiancorp.suiteapi.common.exceptions.AppianRuntimeException: com.appiancorp.suiteapi.common.exceptions.AppianException: Unexpected error executing query (type: [XXXViewDT8164], query: [queryentity expression], order by: [[Sort[userId asc]]], filters:[(userId in TypedValue[it=101,v={5184}])]) (APNX-1-4164-028)

21:35:14,507 INFO [stdout] (Appian Work Item - 59835 - execution15 : ExpressionGroupRequest) Caused by: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 josep
Certified Lead Developer
over 6 years ago in reply to srikanthm0004

Hello Srikanth,

I have been in that error "MySQLTimeoutException" and seems like the timeout is 60 seconds or less so the bet way to approach this issue is as follows:
* Avoid making joins using tables which are large because this might exceed the time used when querying the information.
* If possible and worth it(the size is really big) create a Materialized view, actually this can improve your response time from the DB and the time will be transferred to the "transformation"
* if you still want to deal with the join times use the "Explain select" ti will give you really good hints of the problems and how to solve them.
* filter as much as possible and review indexes on your tables.

hope this helps
jose
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 josep
Certified Lead Developer
over 6 years ago in reply to srikanthm0004

Hello Srikanth,

I have been in that error "MySQLTimeoutException" and seems like the timeout is 60 seconds or less so the bet way to approach this issue is as follows:
* Avoid making joins using tables which are large because this might exceed the time used when querying the information.
* If possible and worth it(the size is really big) create a Materialized view, actually this can improve your response time from the DB and the time will be transferred to the "transformation"
* if you still want to deal with the join times use the "Explain select" ti will give you really good hints of the problems and how to solve them.
* filter as much as possible and review indexes on your tables.

hope this helps
jose
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data