Hide Forgot
Date of First Response: 2009-04-03 07:10:59 project_key: SOA There are errors in jBPM db initalization with MySQL. During startut an exception is thrown 2009-04-03 05:14:40,195 WARN [org.jboss.system.ServiceController] Problem starting service jboss.esb:service=JBPMDatabaseInitializer com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Duplicate key name 'FK_LOG_ACTION' at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:936) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2985) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1631) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1723) at com.mysql.jdbc.Connection.execSQL(Connection.java:3250) at com.mysql.jdbc.Statement.executeUpdate(Statement.java:1355) at com.mysql.jdbc.Statement.executeUpdate(Statement.java:1270) at org.jboss.resource.adapter.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:239) at org.jboss.internal.soa.esb.dependencies.DatabaseInitializer.executeSql(DatabaseInitializer.java:145) at org.jboss.internal.soa.esb.dependencies.DatabaseInitializer.initDatabase(DatabaseInitializer.java:122) at org.jboss.internal.soa.esb.dependencies.DatabaseInitializer.startService(DatabaseInitializer.java:159) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) When the SQL script is run through CLI client it throws ERROR 1061 (42000) at line 93: Duplicate key name 'FK_LOG_ACTION'
This looks like a bug in the jBPM hibernate configuration. Trying a new SOA build with the attached patch for jBPM (SOA-1269.patch).
Attachment: Added: SOA-1269.patch
Revised patch (typo corrected)
Attachment: Removed: SOA-1269.patch
The patch is good. I reviewed the remaining many-to-ones to be sure their name started with IDX as opposed to FK. I will commit the changes, move the tag and redeploy the maven artifacts.
Hold on - something is not right. In HSQLDB (the build did not get as far as MySQL) the following error occurs. 13:02:55,413 WARN (JbpmJobExecutor:127.0.0.1:1) [org.hibernate.util.JDBCExceptionReporter] SQL Error: -177, SQLState: 23000 13:02:55,413 ERROR (JbpmJobExecutor:127.0.0.1:1) [org.hibernate.util.JDBCExceptionReporter] Integrity constraint violation - no parent FK375F591A200A8483 table: JBPM_PROCESSINSTANCE in statement [insert into JBPM_LOG (ID_, INDEX_, DATE_, TOKEN_, PARENT_, VARIABLEINSTANCE_, OLDLONGVALUE_, NEWLONGVALUE_, CLASS_) values (null, ?, ?, ?, ?, ?, ?, ?, 'G')]
Nevermind, I committed an unrelated change along the patch. I have reverted the extraneous change, moved the tag and redeployed the artifacts.
Link: Added: This issue related JBPM-2119
Link: Added: This issue related JBPM-2094
Link: Removed: This issue related JBPM-2119
This is fixed in the (new) jBPM 3.2.5 SP5 tag. This will be incorporated into CR7.
Verified in CR7
Setting new "Affects Testing, Regression, Blocks Testing Fields"
Blocked Tests: Added: jBPM testing with MySQL, perhaps other DBs Affects Testing?: Added: [Regression?, Blocks Testing?]
Re-closing after setting new "Affects Testing, Regression, Blocks Testing Fields"
Edited to match changes in 'affects testing' fields (? character removed from field names for easier querying)
Affects Testing: Removed: [Regression?, Blocks Testing?] Added: [Regression, Blocks Testing]