[jira] [Commented] (OFBIZ-5538) Method getNextSeqId of SequenceUtil.java does not insure that generated id is already exist in DB or not

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (OFBIZ-5538) Method getNextSeqId of SequenceUtil.java does not insure that generated id is already exist in DB or not

Nicolas Malin (Jira)

    [ https://issues.apache.org/jira/browse/OFBIZ-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897688#comment-13897688 ]

Deepak Dixit commented on OFBIZ-5538:
-------------------------------------

Hi Ritu,
We can update the SequenceValueItem data over UAT environment.
If we try to interact db for each getNextSeqId call then it will increase load on DB.

> Method getNextSeqId of SequenceUtil.java does not insure that generated id is already exist in DB or not
> --------------------------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-5538
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5538
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: ALL COMPONENTS
>    Affects Versions: SVN trunk
>            Reporter: Ritu Raj Lakhera
>            Priority: Minor
>             Fix For: SVN trunk
>
>         Attachments: Ofbiz-5538.patch
>
>
> Currently method getNextSeqId of SequenceUtil.java does not insure that generated id is already exist in DB or not.
> The problem is that If we export the production environment's order data to UAT environment and UAT environment order's sequence value(SequenceValueItem) in DB are behind from production.
> So if we create an order on UAT environment then generated order id may exist in DB and code will throw the error until we do not increase the order sequence in DB manually.
> This problem may also arise when we use the two Ofbiz instance, one for e-commerce site only and another for order fulfillment and accounting.
> I think we can modify the method getNextSeqId to generate the sequence id which is not exist in DB.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)