You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacopo Cappellato (JIRA)" <ji...@apache.org> on 2014/08/28 17:22:09 UTC

[jira] [Reopened] (OFBIZ-2353) SequenceUtil may generate duplicate IDs in Load Balancing mode

     [ https://issues.apache.org/jira/browse/OFBIZ-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacopo Cappellato reopened OFBIZ-2353:
--------------------------------------

      Assignee: Jacopo Cappellato  (was: Jacques Le Roux)

[~jacques.le.roux] I have carefully reviewed all these comments and the code that was committed and I am not convinced that the commit was necessary and that fixed the issue reported.
Also, the issue reported in this ticket may be invalid, as the author didn't specify if he was actually experiencing the issue or it was based on his analysis of the code.
On the other hand, [~adrianc@hlmksw.com] mentions some issues happening in an heavily multi threaded environment and I see from the code where this could still happen: I would like to fix it and clean the code that was committed as part of this ticket but please share additional information if you have.

> SequenceUtil  may generate duplicate IDs in Load Balancing mode
> ---------------------------------------------------------------
>
>                 Key: OFBIZ-2353
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2353
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: Release Branch 4.0, Release Branch 09.04, Trunk
>            Reporter: Philippe Mouawad
>            Assignee: Jacopo Cappellato
>            Priority: Critical
>             Fix For: Release Branch 10.04, Release Branch 11.04, Trunk
>
>         Attachments: OFBIZ-2353 SELECT FOR UPDATE solution.patch, OFBIZ-2353 SELECT FOR UPDATE solution.patch
>
>
> If Ofbiz is deploy on 2 servers in Load Balancing Mode
> SequenceUtil will generate duplicate IDs because synchronization is done at JVM level instead of doing it in DB.
> A good replacement implementation would be:
> org.hibernate.id.enhanced.TableGenerator
> But it would involve a dependency on Hibernate
> Philippe
> www.ubik-ingenierie.com



--
This message was sent by Atlassian JIRA
(v6.2#6252)