[jira] Created: (OPENJPA-1372) Generating identifiers by using sequence table may fail during sequence table initialization

Generating identifiers by using sequence table may fail during sequence table initialization
--------------------------------------------------------------------------------------------

                 Key: OPENJPA-1372
                 URL: https://issues.apache.org/jira/browse/OPENJPA-1372
             Project: OpenJPA
          Issue Type: Bug
          Components: jdbc, kernel
    Affects Versions: 2.0.0-M3, 1.2.1
            Reporter: Milosz Tylenda


When sequence table does not exist and mutliple threads get EntityManagers from EntityManageFactory, an insert into sequence table may fail because of duplicate primary key value.

EMF is created lazily by default and users reported various problems with concurrent initialization (e.g. failures in resolving aliases in JPQL queries, IIRC) of EMF. This issue might have the same roots.

Issue and test case originally reported by Pinaki in OPENJPA-466.


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

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

Milosz Tylenda updated OPENJPA-1372:
------------------------------------

    Attachment: TestSequenceGenerationOnMT.java
                GeneratedIdObject.java

> Generating identifiers by using sequence table may fail during sequence table initialization
> --------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1372
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1372
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc, kernel
>    Affects Versions: 1.2.1, 2.0.0-M3
>            Reporter: Milosz Tylenda
>         Attachments: GeneratedIdObject.java, TestSequenceGenerationOnMT.java
>
>
> When sequence table does not exist and mutliple threads get EntityManagers from EntityManageFactory, an insert into sequence table may fail because of duplicate primary key value.
> EMF is created lazily by default and users reported various problems with concurrent initialization (e.g. failures in resolving aliases in JPQL queries, IIRC) of EMF. This issue might have the same roots.
> Issue and test case originally reported by Pinaki in OPENJPA-466.

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