cancel
Showing results for 
Search instead for 
Did you mean: 

Activiti 1.4.1 mysql bug

robinho
Champ in-the-making
Champ in-the-making
Hi

Activiti 1.4.1 bugs if I try to connect it with a mysql database.
I retried with 1.2.1 (this works)

Stracktrace:



INFO 3/1/16 12:40 PM: liquibase: classpath:META-INF/liquibase/db-changelog-onpremise.xml: classpath:META-INF/liquibase/db-changelog-onpremise.xml::1::tijsrademakers: Table hibernate_sequences created
SEVERE 3/1/16 12:40 PM: liquibase: classpath:META-INF/liquibase/db-changelog-onpremise.xml: classpath:META-INF/liquibase/db-changelog-onpremise.xml::1::tijsrademakers: Change Set classpath:META-INF/liquibase/db-
changelog-onpremise.xml::1::tijsrademakers failed.  Error: 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 '(6) NULL, externa
l_id VARCHAR(2000) NULL, last_sync_timestamp timestamp(6) NULL,' at line 1 [Failed SQL: CREATE TABLE `activiti-app`.USERS (id BIGINT NOT NULL, pass_word VARCHAR(100) NULL, first_name VARCHAR(50) NULL, last_name
VARCHAR(50) NULL, email VARCHAR(100) NULL, company VARCHAR(100) NULL, created datetime NULL, status SMALLINT NULL, account_type SMALLINT DEFAULT 1 NULL, tenant_id BIGINT NULL, manager_user_id BIGINT NULL, pictur
e_image_id BIGINT NULL, last_update timestamp(6) NULL, external_id VARCHAR(2000) NULL, last_sync_timestamp timestamp(6) NULL, last_sync_timestamp_epoch BIGINT NULL, CONSTRAINT PK_USERS PRIMARY KEY (id))]
liquibase.exception.DatabaseException: 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 '(6) NULL, external_id VARCHAR(2000) N
ULL, last_sync_timestamp timestamp(6) NULL,' at line 1 [Failed SQL: CREATE TABLE `activiti-app`.USERS (id BIGINT NOT NULL, pass_word VARCHAR(100) NULL, first_name VARCHAR(50) NULL, last_name VARCHAR(50) NULL, em
ail VARCHAR(100) NULL, company VARCHAR(100) NULL, created datetime NULL, status SMALLINT NULL, account_type SMALLINT DEFAULT 1 NULL, tenant_id BIGINT NULL, manager_user_id BIGINT NULL, picture_image_id BIGINT NU
LL, last_update timestamp(6) NULL, external_id VARCHAR(2000) NULL, last_sync_timestamp timestamp(6) NULL, last_sync_timestamp_epoch BIGINT NULL, CONSTRAINT PK_USERS PRIMARY KEY (id))]
        at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:316)
        at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:55)
        at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:122)
        at liquibase.database.AbstractJdbcDatabase.execute(AbstractJdbcDatabase.java:1247)
        at liquibase.database.AbstractJdbcDatabase.executeStatements(AbstractJdbcDatabase.java:1230)
        at liquibase.changelog.ChangeSet.execute(ChangeSet.java:548)
        at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:51)
        at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:73)
        at liquibase.Liquibase.update(Liquibase.java:210)
        at liquibase.Liquibase.update(Liquibase.java:190)
        at liquibase.integration.spring.SpringLiquibase.performUpdate(SpringLiquibase.java:434)
        at liquibase.integration.spring.SpringLiquibase.afterPropertiesSet(SpringLiquibase.java:391)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1633)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1570)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:539)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476)
        at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:303)
        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:299)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:755)
        at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:757)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:480)
        at com.activiti.servlet.WebConfigurer.contextInitialized(WebConfigurer.java:85)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4738)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5181)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
        at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:945)
        at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1798)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
3 REPLIES 3

jbarrez
Star Contributor
Star Contributor
Which mySQL version? We all use MySQL in development, so this sounds very odd that it happens with MySQL.

robinho
Champ in-the-making
Champ in-the-making
mysql  Ver 14.14 Distrib 5.5.44, for debian-linux-gnu (x86_64)
I removed this mysql version.

I installed mySql 5.6.28
Now it works!

Thanks anyway I should have upgraded mysql earlier

jbarrez
Star Contributor
Star Contributor
Ah yes, it should be 5.6+. The reason is that 5.5 has low precision when it comes to storing timestamps (which is quite important for audit logs for example).