[ http://jira.jboss.com/jira/browse/JBPM-85?page=history ]
Tom Baeyens updated JBPM-85:
----------------------------
Component: Core Engine
> SequenceBlockIdGenerator produces duplicate keys
> ------------------------------------------------
>
> Key: JBPM-85
> URL: http://jira.jboss.com/jira/browse/JBPM-85
> Project: JBoss jBPM
> Type: Bug
> Components: Core Engine
> Versions: jBPM 2.0
> Environment: jbpm 2.0, jboss 4.01, jdk1.5
> Reporter: Armin Haaf
> Assignee: Tom Baeyens
>
>
> 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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
