I have a local installation of Aggregate. My tomcat server is aborting by
itself for some reason, and I have to restart it again manually. Following
are the traces:
org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback;
bad SQL grammar [SELECT _URI, _CREATOR_URI_USER, _CREATION_DATE, _LAST_UPDATE_URI_USER, _LAST_UPDATE_DATE, TABLE_ID, TABLE_KEY, DB_TABLE_NAME, TYPE, TABLE_ID_ACCESS_CONTROLS FROM odk_prod.__ODKTABLES__TABLE_DEFINITIONS WHERE TABLE_ID IN ();];
nested exception is
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an
error in your SQL syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near ')' at line 1
I suspect that it might be because of very heavy data submission (high
megapix images), is it? I might be wrong though.
Can someone plz let me know any diagnosis/resolution?
Go to the Site Admin / Preferences screen and uncheck 'ODK Tables
Syncronization Functionality'
If this does not resolve the issue, I will look into a more involved
work-around.
The bug was introduced in v1.3.2. If you do not need the bug fixes in
1.3.2, and if the above checkbox does not resolve the issue you can install
1.3.1.
We are close to releasing an update to ODK Aggregate with the bug fix for
this.
Mitch
···
On Thu, Aug 29, 2013 at 5:08 AM, Saad Omer wrote:
Hi,
I have a local installation of Aggregate. My tomcat server is aborting by
itself for some reason, and I have to restart it again manually. Following
are the traces:
org.springframework.jdbc.BadSqlGrammarException:
PreparedStatementCallback; bad SQL grammar [SELECT _URI, _CREATOR_URI_USER, _CREATION_DATE, _LAST_UPDATE_URI_USER, _LAST_UPDATE_DATE, TABLE_ID, TABLE_KEY, DB_TABLE_NAME, TYPE, TABLE_ID_ACCESS_CONTROLS FROM odk_prod.__ODKTABLES__TABLE_DEFINITIONS
WHERE TABLE_ID IN ();]; nested exception is
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an
error in your SQL syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near ')' at line 1
I suspect that it might be because of very heavy data submission (high
megapix images), is it? I might be wrong though.
Can someone plz let me know any diagnosis/resolution?
ODK tables sync functionality is already unchecked.
I seem to have figured out the issue with tomcat; its running short of RAM
space, hence it aborts. However, the issue with MySQL syntax error in log
is still there.
···
On Thu, Aug 29, 2013 at 9:08 PM, Mitch Sundt wrote:
Go to the Site Admin / Preferences screen and uncheck 'ODK Tables
Syncronization Functionality'
If this does not resolve the issue, I will look into a more involved
work-around.
The bug was introduced in v1.3.2. If you do not need the bug fixes in
1.3.2, and if the above checkbox does not resolve the issue you can install
1.3.1.
We are close to releasing an update to ODK Aggregate with the bug fix for
this.
Mitch
On Thu, Aug 29, 2013 at 5:08 AM, Saad Omer saad@saadaan.com wrote:
Hi,
I have a local installation of Aggregate. My tomcat server is aborting by
itself for some reason, and I have to restart it again manually. Following
are the traces:
org.springframework.jdbc.BadSqlGrammarException:
PreparedStatementCallback; bad SQL grammar [SELECT _URI, _CREATOR_URI_USER, _CREATION_DATE, _LAST_UPDATE_URI_USER, _LAST_UPDATE_DATE, TABLE_ID, TABLE_KEY, DB_TABLE_NAME, TYPE, TABLE_ID_ACCESS_CONTROLS FROM odk_prod.__ODKTABLES__TABLE_DEFINITIONS
WHERE TABLE_ID IN ();]; nested exception is
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an
error in your SQL syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near ')' at line 1
I suspect that it might be because of very heavy data submission (high
megapix images), is it? I might be wrong though.
Can someone plz let me know any diagnosis/resolution?
Ah, OK. I'm glad that the error is not crashing Tomcat. The fix will be in
the next release.
···
On Thu, Aug 29, 2013 at 9:28 AM, Saad Omer wrote:
ODK tables sync functionality is already unchecked.
I seem to have figured out the issue with tomcat; its running short of RAM
space, hence it aborts. However, the issue with MySQL syntax error in log
is still there.
Go to the Site Admin / Preferences screen and uncheck 'ODK Tables
Syncronization Functionality'
If this does not resolve the issue, I will look into a more involved
work-around.
The bug was introduced in v1.3.2. If you do not need the bug fixes in
1.3.2, and if the above checkbox does not resolve the issue you can install
1.3.1.
We are close to releasing an update to ODK Aggregate with the bug fix for
this.
Mitch
On Thu, Aug 29, 2013 at 5:08 AM, Saad Omer saad@saadaan.com wrote:
Hi,
I have a local installation of Aggregate. My tomcat server is aborting
by itself for some reason, and I have to restart it again manually.
Following are the traces:
org.springframework.jdbc.BadSqlGrammarException:
PreparedStatementCallback; bad SQL grammar [SELECT _URI, _CREATOR_URI_USER, _CREATION_DATE, _LAST_UPDATE_URI_USER, _LAST_UPDATE_DATE, TABLE_ID, TABLE_KEY, DB_TABLE_NAME, TYPE, TABLE_ID_ACCESS_CONTROLS FROM odk_prod.__ODKTABLES__TABLE_DEFINITIONS
WHERE TABLE_ID IN ();]; nested exception is
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an
error in your SQL syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near ')' at line 1
I suspect that it might be because of very heavy data submission (high
megapix images), is it? I might be wrong though.
Can someone plz let me know any diagnosis/resolution?