Okay, one day later and one small step further, I compared the logs of the JTA-run:
| [org.jbpm.configuration.JbpmContextInfo] creating jbpm context with service factories '[tx, message, scheduler, logging, persistence, authentication]' | [org.jbpm.JbpmContext] creating [EMAIL PROTECTED] | [com.camunda.toolkit.jbpm.service.CommandServiceBean] executing [EMAIL PROTECTED] | [org.jbpm.command.DeployProcessCommand] parse process from String | [org.jbpm.command.DeployProcessCommand] deploy process: <process-definition name='Test2'><start-state name='start'></start-state></process-definition> | [org.jbpm.graph.node.NodeTypes] node 'page' will not be available. class 'org.jboss.seam.pageflow.Page' couldn't be loaded | [org.jbpm.graph.node.NodeTypes] node 'start-page' will not be available. class 'org.jboss.seam.pageflow.Page' couldn't be loaded | [org.jbpm.persistence.db.DbPersistenceServiceFactory] creating persistence service | [org.jbpm.persistence.db.DbPersistenceService] creating hibernate session | [org.jbpm.persistence.db.DbPersistenceService] beginning hibernate transaction | [STDOUT] Hibernate: select processdef0_.ID_ as ID1_50_, processdef0_.NAME_ as NAME3_50_, processdef0_.DESCRIPTION_ as DESCRIPT4_50_, processdef0_.VERSION_ as VERSION5_50_, processdef0_.ISTERMINATIONIMPLICIT_ as ISTERMIN6_50_, processdef0_.STARTSTATE_ as STARTSTATE7_50_ from JBPM_PROCESSDEFINITION processdef0_ where processdef0_.NAME_=? order by processdef0_.VERSION_ desc limit ? | [STDOUT] Hibernate: insert into JBPM_PROCESSDEFINITION (NAME_, DESCRIPTION_, VERSION_, ISTERMINATIONIMPLICIT_, STARTSTATE_, CLASS_) values (?, ?, ?, ?, ?, 'P') | [STDOUT] Hibernate: insert into JBPM_NODE (NAME_, DESCRIPTION_, PROCESSDEFINITION_, ISASYNC_, ISASYNCEXCL_, ACTION_, SUPERSTATE_, CLASS_) values (?, ?, ?, ?, ?, ?, ?, 'R') | [STDOUT] Hibernate: insert into JBPM_MODULEDEFINITION (NAME_, PROCESSDEFINITION_, CLASS_) values (?, ?, 'C') | [STDOUT] Hibernate: insert into JBPM_MODULEDEFINITION (NAME_, PROCESSDEFINITION_, STARTTASK_, CLASS_) values (?, ?, ?, 'T') | [org.jbpm.command.DeployProcessCommand] deployment sucessfull | [com.camunda.toolkit.jbpm.service.CommandServiceBean] ... finished with [EMAIL PROTECTED] | [org.jbpm.JbpmContext] closing JbpmContext | [org.jbpm.svc.Services] closing service 'persistence': [EMAIL PROTECTED] | [org.jbpm.persistence.db.DbPersistenceService] committing hibernate transaction | [org.jbpm.persistence.db.DbPersistenceService] closing hibernate session | [org.jbpm.svc.Services] closing service 'tx': [EMAIL PROTECTED] | [org.jbpm.svc.Services] closing service 'authentication': [EMAIL PROTECTED] | and the local Testrun: | [main] DEBUG DbPersistenceService : creating hibernate session | [main] DEBUG DbPersistenceService : beginning hibernate transaction | [main] DEBUG AbstractDbTestCase : | [main] DEBUG AbstractDbTestCase : ### starting testProcessDefinitionStartState #################################################### | [main] INFO DeployProcessCommand : parse process from String | [main] DEBUG DeployProcessCommand : deploy process: <process-definition name='Test2'><start-state name='start'></start-state></process-definition> | [main] DEBUG NodeTypes : node 'page' will not be available. class 'org.jboss.seam.pageflow.Page' couldn't be loaded | [main] DEBUG NodeTypes : node 'start-page' will not be available. class 'org.jboss.seam.pageflow.Page' couldn't be loaded | Hibernate: select processdef0_.ID_ as ID1_0_, processdef0_.NAME_ as NAME3_0_, processdef0_.DESCRIPTION_ as DESCRIPT4_0_, processdef0_.VERSION_ as VERSION5_0_, processdef0_.ISTERMINATIONIMPLICIT_ as ISTERMIN6_0_, processdef0_.STARTSTATE_ as STARTSTATE7_0_ from JBPM_PROCESSDEFINITION processdef0_ where processdef0_.NAME_=? order by processdef0_.VERSION_ desc limit ? | Hibernate: insert into JBPM_PROCESSDEFINITION (NAME_, DESCRIPTION_, VERSION_, ISTERMINATIONIMPLICIT_, STARTSTATE_, CLASS_) values (?, ?, ?, ?, ?, 'P') | Hibernate: insert into JBPM_NODE (NAME_, DESCRIPTION_, PROCESSDEFINITION_, ISASYNC_, ISASYNCEXCL_, ACTION_, SUPERSTATE_, CLASS_) values (?, ?, ?, ?, ?, ?, ?, 'R') | Hibernate: insert into JBPM_MODULEDEFINITION (NAME_, PROCESSDEFINITION_, CLASS_) values (?, ?, 'C') | Hibernate: insert into JBPM_MODULEDEFINITION (NAME_, PROCESSDEFINITION_, STARTTASK_, CLASS_) values (?, ?, ?, 'T') | [main] INFO DeployProcessCommand : deployment sucessfull | [main] DEBUG AbstractDbTestCase : ### testProcessDefinitionStartState done #################################################### | [main] DEBUG AbstractDbTestCase : | [main] DEBUG JbpmContext : closing JbpmContext | [main] DEBUG Services : closing service 'persistence': [EMAIL PROTECTED] | [main] DEBUG DbPersistenceService : committing hibernate transaction | Hibernate: update JBPM_PROCESSDEFINITION set NAME_=?, DESCRIPTION_=?, VERSION_=?, ISTERMINATIONIMPLICIT_=?, STARTSTATE_=? where ID_=? | Hibernate: update JBPM_NODE set PROCESSDEFINITION_=?, NODECOLLECTIONINDEX_=? where ID_=? | Hibernate: update JBPM_MODULEDEFINITION set PROCESSDEFINITION_=?, NAME_=? where ID_=? | Hibernate: update JBPM_MODULEDEFINITION set PROCESSDEFINITION_=?, NAME_=? where ID_=? | [main] DEBUG DbPersistenceService : closing hibernate session | [main] DEBUG Services : closing service 'tx': [EMAIL PROTECTED] | Really eye-catching is, that in the local Testrun, there are some additonal UPDATES, which are missing in the JTA version. I think, they correct the ID's, because the ID's were generated from the database during the first INSERT and so not known in advance. So we really need these second updates for the many-to-one associations. But why is that missing in the JTA version? May some small implementation issue in jbpm 3.2. I will investigate further. And I have created a JIRAA-Issue for that: http://jira.jboss.com/jira/browse/JBPM-944 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035668#4035668 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035668 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user