]
Ronald van Kuijk closed JBPM-85.
--------------------------------
Resolution: Out of Date
jbpm 2!!!!
SequenceBlockIdGenerator produces duplicate keys
------------------------------------------------
Key: JBPM-85
URL:
http://jira.jboss.com/jira/browse/JBPM-85
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM 2.0
Environment: jbpm 2.0, jboss 4.01, jdk1.5
Reporter: Armin Haaf
Assigned To: Tom Baeyens
Priority: Optional
SequenceBlockIdGenerator produces duplicate keys, if the transaction in which the hilo
block is read from the database is rollbacked. This could occur in a j2ee environment in a
jta transaction. I´m not sure if a hibernate session using jta transactions creates a new
jta transaction, if a transaction is already registered, but it seems it uses the current
transaction. So the beginTransaction, commit code in SequenceBlockIdGenerator did not
commit immediatly and could be rollbacked later.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: