topic Re: Duplicate Row error on redeploy of BPMN file, Activiti 5.10 in Alfresco Archive

Duplicate Row error on redeploy of BPMN file, Activiti 5.10

mindcrime — Fri, 22 Mar 2013 15:27:54 GMT

Fellow Aciviti'ers:I'm seeing some strange behaviour when redeploying a BPMN file through Activiti Explorer. This only seemsto happen if the BPMN in question has running processes associated with it. In this case, when youupload the new BPMN, the following error is encountered. The DB2 SQLSTATE

Re: Duplicate Row error on redeploy of BPMN file, Activiti 5.10

frederikherema1 — Fri, 22 Mar 2013 15:44:01 GMT

Is it a single process BPMN-fiel you deploy or is it a BAR-file? Do you see the same behavior on the default H2-db (if it's possible to test this in your environment with your processes).

Re: Duplicate Row error on redeploy of BPMN file, Activiti 5.10

mindcrime — Fri, 22 Mar 2013 15:53:27 GMT

Is it a single process BPMN-fiel you deploy or is it a BAR-file? Do you see the same behavior on the default H2-db (if it's possible to test this in your environment with your processes).

It's a single .bpmn20.xml file. I might be able to setup an H2 based environment to test this, but it'll take a little bit of work, as our current dev environment is all DB2 based.

I have tried a similar experiment with a local install of Activiti Explorer, backed by PostgreSQL, and can confirm that - in at least some circumstances - redeploying a BPMN, even if it has associated running instances - works OK. But the BPMN I was experimenting with in that environment wasn't the same one I was using in dev. So right now, I don't know if it's more likely that the problem is something to do with the difference between PostgreSQL / DB2, or if it involves a difference in the actual process definition itself.

I'll keep doing some more experiments here and see if I can narrow things down a bit…

Re: Duplicate Row error on redeploy of BPMN file, Activiti 5.10

mindcrime — Mon, 25 Mar 2013 16:04:37 GMT

OK, I experimented with this some more. Here's the deal: Using a specific BPMN, I can deploy, start, redeploy - with no errors - using an Activiti Explorer instance backed by PostreSQL. However, using an instance backed by DB/2, using the exact same BPMN file, redeploy results in the "duplicate row" error listed above. So this does appear to be something specific to the DB/2 support.

My first hunch is that the db scripts may not be creating the unique constraint correctly on DB/2. I'll start examining that, but if anyone else has any ideas or suggestions, I'm all ears. I really need to get this working for a client, and DB/2 is - for better or worse - non-negotiable here.

Thanks!

Re: Duplicate Row error on redeploy of BPMN file, Activiti 5.10

jbarrez — Tue, 26 Mar 2013 09:40:58 GMT

Hmm sounds really strange. Would you be able to inspect the contents of the db before the exception happens?

Could you also set the log level to debug, that way you can see what data is going into the database.

Re: Duplicate Row error on redeploy of BPMN file, Activiti 5.10

mindcrime — Tue, 26 Mar 2013 14:27:33 GMT

Hmm sounds really strange. Would you be able to inspect the contents of the db before the exception happens?

Could you also set the log level to debug, that way you can see what data is going into the database.

I attached a remote debugger and stepped through the deploy process yesterday, although I didn't quite find exactly where the error is occurring. I'm not very familiar with that part of the Activiti code, nor with iBatis, unfortunately. However, my suspicion now is that the problem has something to do with the primary key generation for new persistent objects. I'm going to switch Activiti Explorer over to using UUIDs and test that, as a quick "spike" to see if it solves the problem. If it does, we're actually fine, since we were planning to go with UUIDs anyway. If that doesn't work, I'll try setting the logs to debug, and/or doing some additional exploration with the debugger.

One quick side note, which may or may not be relevant… looking at my console log from yesterday, it looks like one attempt to redeploy this BPMN resulted in that same error message / stacktrace being printed four times. Not sure if maybe there's some retry logic in there, or if the error is just being logged multiple times or what.

Re: Duplicate Row error on redeploy of BPMN file, Activiti 5.10

mindcrime — Tue, 26 Mar 2013 15:44:02 GMT

OK, I think I have this figured out. In our DEV db, there is a unique constraint on the 'NAME' column of the ACT_RE_DEPLOYMENT table. This constraint is not present in, for example, my local PostgreSQL instance.

Strangely enough, the constraint name is 'ACT_UNIQ_RE_DEPLOY_NAME' but I grepped through the Activiti 5.10 source and could not find that symbol anywhere. Does anyone know if maybe that's a throwback to a previous version of Activiti or something? The client claim they didn't make any changes to the Activiti db, so I'm assuming it go put there by the Activiti install script, at some point.

Re: Duplicate Row error on redeploy of BPMN file, Activiti 5.10

frederikherema1 — Wed, 27 Mar 2013 12:09:06 GMT

It seems like that is a remainder from the initial "experimental" DB2-support. This constraint can be safely dropped, as it makes no sense to be on the table. Anyhow, 5.10+ doesn't contain this constraint anymore, maybe that's why not many people run into this issue. Thanks for sharing!