How can you be sure it was single threaded? Sent from my iPhone
On Sep 12, 2011, at 1:00 PM, "Gabe Resneck (JIRA)" <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/OODT-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102801#comment-13102801 > ] > > Gabe Resneck commented on OODT-314: > ----------------------------------- > > While I do agree that the methods of the MemoryJobRepository class need to be > synchronized, I don't think that it's a multithreading issue that is causing > this bug since it occurred on my machine in a single-threaded context. I ran > into the bug while unit testing changes to the JobQueue implementations. > Jobs were being assigned the same ID. > >> 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 >> >> >> 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 > >
