Bug 777889 (SOA-417)

Summary: bpm_orchestration2 generates "[JDBCExceptionReporter] Concurrent update" errors on multi-cpu systems
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Len DiMaggio <ldimaggi>
Component: JBPM - within SOAAssignee: Thomas Diesler <thomas.diesler>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2 CR3   
Target Milestone: ---   
Target Release: 4.3 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-417
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
/opt/RC3/soa-4.2.0.CR3.zip /opt/RC3/standalone-soa-4.2.0.CR3.zip
Last Closed: 2008-09-29 11:54:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 777950    
Attachments:
Description Flags
server.log.gz
none
server.log
none
server.log
none
Feb12_embedded_server.log.bz2
none
Feb12_standalone_server.log.bz2
none
Feb12_embedded_all_hsqldb_server.log.bz2
none
Feb12_production_hsqldb_server.log.bz2
none
server.log
none
server.log.gz
none
server.log.gz none

Description Len DiMaggio 2008-02-11 18:32:37 UTC
Date of First Response: 2008-02-13 13:22:50
project_key: SOA

Seeing this exception (server.log attached) - in CR3 with bmp_orchestration2 - with HSQLDB.

Steps to recreate:
1) cp jboss-soa-p.4.2.0/jboss-as/tools/resources/jbpm-console-development.war jboss-soa-p.4.2.0/jboss-as/server/all/deploy/jbpm.esb/jbpm-console.war 
2) ant deploy
3) ant deployProcess
4) ant startProcess

13:20:51,135 ERROR [JDBCExceptionReporter] Concurrent update in table JBPM_TOKEN: another transaction has updated or deleted the same row [90131-66]
13:20:51,136 ERROR [AbstractFlushingEventListener] Could not synchronize database state with session
org.hibernate.exception.GenericJDBCException: could not update: [org.jbpm.graph.exe.Token#1]
        at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)
        at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)
        at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
        at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2425)
        at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2307)

Comment 2 Len DiMaggio 2008-02-11 18:33:10 UTC
Server log - 'all' server

Comment 3 Len DiMaggio 2008-02-11 18:33:10 UTC
Attachment: Added: server.log.gz


Comment 4 Len DiMaggio 2008-02-11 18:33:28 UTC
Link: Added: This issue is related to SOA-409


Comment 5 Len DiMaggio 2008-02-11 18:33:28 UTC
Link: Added: This issue is related to SOA-410


Comment 7 Len DiMaggio 2008-02-11 19:31:50 UTC
Attachment: Added: server.log


Comment 8 Len DiMaggio 2008-02-11 20:29:00 UTC
Seeing the sam errors/warnings with Postgresql (production config)



Comment 9 Len DiMaggio 2008-02-11 20:29:00 UTC
Attachment: Added: server.log


Comment 12 Len DiMaggio 2008-02-12 17:38:16 UTC
Attachment: Added: Feb12_embedded_server.log.bz2
Attachment: Added: Feb12_standalone_server.log.bz2


Comment 14 Len DiMaggio 2008-02-12 18:06:42 UTC
Attachment: Added: Feb12_embedded_all_hsqldb_server.log.bz2
Attachment: Added: Feb12_production_hsqldb_server.log.bz2


Comment 15 Aleksandar Kostadinov 2008-02-13 18:22:50 UTC
I tried this one 100 times with a local mysql instance to avoid network delays and it didn't occur. I tried on 2 CPU dual core AMD system. So it doesn't occur with mysql.

Comment 16 Aleksandar Kostadinov 2008-02-13 18:23:31 UTC
Link: Added: This issue related SOA-415


Comment 17 Aleksandar Kostadinov 2008-02-14 14:55:45 UTC
All tier1 databases tested to not produce any errors in 100 runs. So probably it's hsqldb that doesn't support transactions. Marking as passed in testify.

Comment 18 Kevin Conner 2008-03-18 14:04:43 UTC
Link: Removed: This issue is related to SOA-409 


Comment 19 Len DiMaggio 2008-03-18 17:57:44 UTC
With the GA bits - on a multi-processor system - seeing the exception first listed in:
    http://jira.jboss.com/jira/browse/SOA-417#action_12399166

WARN  [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline

And this error:

ERROR [org.jboss.resource.adapter.jms.inflow.JmsServerSession] Unexpected error delivering message delegator->JBossMessage[29]:PERSISTENT, deliveryId=7
org.jbpm.JbpmException: couldn't execute org.jboss.soa.esb.services.jbpm.cmd.CallbackCommand@a6cac9

server.log file is attached - this is with an out-of-the-box configuration using hsqldb/h2.



Comment 20 Len DiMaggio 2008-03-18 17:57:44 UTC
Attachment: Added: server.log


Comment 21 Len DiMaggio 2008-03-18 18:28:31 UTC
This is similar to the latest attached files to http://jira.jboss.com/jira/browse/SOA-410 in that with the GA bits, the error is now not being seen with postgresql. See attached server.log

Comment 22 Len DiMaggio 2008-03-18 18:28:31 UTC
Attachment: Added: server.log.gz


Comment 23 Len DiMaggio 2008-03-18 18:30:40 UTC
Question - is this also a problem with H2 - ala:  http://jira.jboss.com/jira/browse/SOA-409#action_12403386

Comment 24 Len DiMaggio 2008-03-18 18:32:59 UTC
The problem does seem to be specific to an out-of-the box configuration with hsqldb/h2.

With postgres as the DB, the problem is not seen. See attached server.log file.

So - Alex's comment:
http://jira.jboss.com/jira/browse/SOA-417#action_12399441

Is correct - as hsqldb/h2 are not tier1 DBs - but - the error will be seen by customers running the quickstart with the out-of-the box configuration of hsqldb/h2.

Comment 25 Mark Little 2008-03-28 09:39:35 UTC
Link: Added: This issue is a dependency of SOA-480


Comment 26 Len DiMaggio 2008-07-17 14:07:59 UTC
Time to close this JIRA - the problem never had any real functional/operational impact.

And - with CP02_CR5 - it's not reproducible - see attached server log file.

Comment 27 Len DiMaggio 2008-07-17 14:07:59 UTC
Attachment: Added: server.log.gz


Comment 28 Len DiMaggio 2008-07-17 14:08:22 UTC
Time to close this JIRA - the problem never had any real functional/operational impact.

And - with CP02_CR5 - it's not reproducible - see attached server log file.

Comment 29 nwallace 2008-09-26 06:05:01 UTC
Link: Added: This issue related SOA-869