Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <1699234684.1247090835066.JavaMail.jira@brutus>
Date: Wed, 8 Jul 2009 15:07:15 -0700 (PDT)
From: "Rick Curtis (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Updated: (OPENJPA-1168) NPE in
 UUIDGenerator.initializeForType1()
In-Reply-To: <2053572264.1247090475560.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/OPENJPA-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Curtis updated OPENJPA-1168:
---------------------------------

    Patch Info: [Patch Available]
      Assignee:     (was: Rick Curtis)

> NPE in UUIDGenerator.initializeForType1()
> -----------------------------------------
>
>                 Key: OPENJPA-1168
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1168
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: lib
>            Reporter: Rick Curtis
>             Fix For: 1.3.0, 2.0.0
>
>         Attachments: OPENJPA-1168.patch
>
>
> When UUIDGenerator.createType1() is called by more than one thread at *nearly* the same time AND UUIDGenerator.createType1() wasn't called previously, a small timing window exists where a NPE will result.
> Scenario:
> Thread 1 calls UUIDGenerator.createType1() and RANDOM == null so initializeForType1() is called. While that thread is in initializeForType1(), it sets the static variable RANDOM so that value is no longer null. Now Thread 2 calls UUIDGenerator.createType1() and RANDOM is no longer null, so it proceeds to the call System.arraycopy(IP, 0, uuid, 10, IP.length);. At this point Thread 1 hasn't got to initializing IP yet, so Thread 2 gets hits a NPE.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.