I get "attempt to insert duplicate key row" kind of database errors all the 
time while executionService.close() is running. Somehow jbpm tries to insert a 
row double times or sometimes with wrong parameters.

An example trace is as below:

12:58:28,624 INFO  [STDOUT] 12:58:28,624 trace [EntityPersister] Inserting 
entity: [org.jbpm.model.execution.impl.TokenImpl#6553993]
  | 12:58:28,624 INFO  [STDOUT] 12:58:28,624 trace [BatcherImpl] about to open: 
0 open PreparedStatements, 0 open ResultSets
  | 12:58:28,624 INFO  [STDOUT] 12:58:28,624 debug [SQL] insert into JBPM_TOKEN 
(name, processInstance, parent, state, actorId, start_, end_, reactivationJoin, 
subProcessInstance, lastStateLog, id) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
  | 12:58:28,634 INFO  [STDOUT] 12:58:28,624 trace [BatcherImpl] preparing 
statement
  | 12:58:28,634 INFO  [STDOUT] 12:58:28,634 trace [EntityPersister] 
Dehydrating entity: [org.jbpm.model.execution.impl.TokenImpl#6553993]
  | 12:58:28,634 INFO  [STDOUT] 12:58:28,634 trace [StringType] binding 'root' 
to parameter: 1
  | 12:58:28,634 INFO  [STDOUT] 12:58:28,634 trace [LongType] binding null to 
parameter: 2
  | 12:58:28,634 INFO  [STDOUT] 12:58:28,634 trace [LongType] binding null to 
parameter: 3
  | 12:58:28,634 INFO  [STDOUT] 12:58:28,634 trace [LongType] binding 
'13107241' to parameter: 4
  | 12:58:28,634 INFO  [STDOUT] 12:58:28,634 trace [StringType] binding null to 
parameter: 5
  | 12:58:28,634 INFO  [STDOUT] 12:58:28,634 trace [TimestampType] binding 
'2005-12-29 12:58:27' to parameter: 6
  | 12:58:28,634 INFO  [STDOUT] 12:58:28,634 trace [TimestampType] binding null 
to parameter: 7
  | 12:58:28,634 INFO  [STDOUT] 12:58:28,634 trace [LongType] binding null to 
parameter: 8
  | 12:58:28,634 INFO  [STDOUT] 12:58:28,634 trace [LongType] binding null to 
parameter: 9
  | 12:58:28,634 INFO  [STDOUT] 12:58:28,634 trace [LongType] binding null to 
parameter: 10
  | 12:58:28,634 INFO  [STDOUT] 12:58:28,634 trace [LongType] binding '6553993' 
to parameter: 11


Does anybody know a possible solution to this?




View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3914721#3914721

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3914721


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to