[
https://issues.apache.org/jira/browse/OFBIZ-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897714#comment-13897714
]
Ritu Raj Lakhera commented on OFBIZ-5538:
-----------------------------------------
Thanks Deepak for looking in this.
This is good to increase the SequenceValueItem data on UAT.
But If I use the two Ofbiz instance, one for e-commerce site(B2C) only and
second for order fulfillment and accounting. And second instance is also used
for B2B customer.
That time the second instance may throw the error for new order id and then we
need to increase the SequenceValueItem every time.
I think this will stop these unexpected error and improve the utility
> 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)
