[
https://issues.apache.org/jira/browse/UIMA-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849682#comment-16849682
]
Lou DeGenaro commented on UIMA-6036:
------------------------------------
The reporter noticed that after booting DUCC, some artifacts (Managed
Reservations) had duplicate ID numbers.
Was not able to reproduce. ID numbers, including Managed Reservations, are
persisted by the OR to the DB. And upon boot, the OR reads from the DB to
initialize the next available ID sequence number. Confirmed proper operation
by code inspection and testing. Test was to create some Managed Reservations,
re-boot DUCC, and confirm that the next ID number was the next in sequence,
which it was.
The reported problem may possibly be explained by Jira 6049.
> ducc_id not updated correctly after restoring DB from backup
> ------------------------------------------------------------
>
> Key: UIMA-6036
> URL: https://issues.apache.org/jira/browse/UIMA-6036
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Affects Versions: 3.0.0-Ducc
> Reporter: Eddie Epstein
> Priority: Major
> Fix For: 3.0.1-Ducc
>
>
> After restoring a DB from backup the next value of ducc_id is not chosen
> correctly. It is leaving out previous reservations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
