Thanks gave I'll check it out. I'm not sure how in a non threaded app new Date() would ever generate the same time but I'll check...
Sent from my iPhone On Sep 12, 2011, at 6:10 PM, "Gabe Resneck (JIRA)" <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/OODT-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Gabe Resneck updated OODT-314: > ------------------------------ > > Attachment: TestFifoMappedJobQueue.java > > I ran into the bug while running the testPromoteJob() test method. You will > see that two jobs are added to the queue (and, as a result, also the job > repo) back to back. I don't think that this is a threading issue because > this is done inside the same test, which would all be done on one thread. I > probably just should have posted this to begin with. My bad. > >> It is possible for 2 jobs submitted at very similar times to be assigned the >> same ID by the MemoryJobRepository >> --------------------------------------------------------------------------------------------------------------- >> >> Key: OODT-314 >> URL: https://issues.apache.org/jira/browse/OODT-314 >> Project: OODT >> Issue Type: Bug >> Components: resource manager >> Reporter: Gabe Resneck >> Assignee: Gabe Resneck >> Fix For: 0.4 >> >> Attachments: TestFifoMappedJobQueue.java >> >> >> Currently, when a job is added to a MemoryJobRepository, it helps to ensure >> no duplicates by assigning a new ID to that job based upon the current time. >> However, it is still possible for jobs to be assigned the same ID if they >> are submitted at very similar times. > > -- > This message is automatically generated by JIRA. > For more information on JIRA, see: http://www.atlassian.com/software/jira > >
