search

xornand / alfresco-business-reporting

Automatically exported from code.google.com/p/alfresco-business-reporting
0 stars 0 forks source link

Reporting tables not getting loaded during alfresco startup #31

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
I am seeing this error during Alfresco startup when reporting tables are 
accessed:

10:41:17,415 INFO  [QuartzScheduler] JobFactory set to: 
org.alfresco.repo.scheduler.AlfrescoJobFactory@48f4d2c8

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 ''�2<x�' at line 1

Do you have any recommendation to resolve this?

Thanks!

Original issue reported on code.google.com by shyla...@gmail.com on 21 Nov 2013 at 6:48

GoogleCodeExporter commented 8 years ago 
I am afraid you have to solve issue #27 first.. If that does not work, I can 
imagine this issue is suffering from the same cause...

Original comment by tjarda.p...@incentro.com on 24 Nov 2013 at 8:21

GoogleCodeExporter commented 8 years ago 
Thank you!

Connection issue in issue #27  is not an issue anymore as I am feeding DB 
values from properties file. A comment is added in #27 explaining this.

How is this related to issue#27?

Thanks,
Shyla

Original comment by shyla...@gmail.com on 25 Nov 2013 at 2:00

GoogleCodeExporter commented 8 years ago 
Sorry for the delay in answering... It is a bit busy over here...

Issue 27 is about the non-functional JNDI connection. This connection is used 
in two times: 
1) When Harvesting to store content into the reporting database. This part can 
potentially be worked around by using direct JDBC properties. (It will be 
removed in the next version for your information...)
2) When executing reports the embedded Pentaho module will get the report 
definition, and just execute. This will work if you store the JNDI name into 
the report, the SDK will find out how to get the connection details. 

The reason for using JNDI is to have reports portable. You create them on a 
given development client. They need to be executed on this development client, 
the test-server, acceptance environment and production...

When starting Alfresco the system will get the row-count of the tables, thus 
accessing the reporting database. Since JNDI is the preferred way, I can 
imagine the JDBC version will fail..

If JNDI does not work while getting metadata from Alfresco into the reporting 
database, executing reports won't work either, they use JNDI too...

Original comment by tjarda.p...@incentro.com on 5 Dec 2013 at 9:16