[
https://issues.apache.org/jira/browse/OPENJPA-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680527#action_12680527
]
David Jencks commented on OPENJPA-969:
--------------------------------------
I've never got openJPA to work on geronimo with derby with one (jta)
datasource. I haven't been able to figure out exactly what is going on but I
think that either during or after the transaction context switch to a "requires
new" transaction for sequence table access derby loses track of which schema it
is using and can't find _any_ tables.
> In the J2ee environment, when the sequence table is used for identity, if
> only one datasource is created, the application hangs.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-969
> URL: https://issues.apache.org/jira/browse/OPENJPA-969
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.0.0
> Reporter: Fay Wang
> Assignee: Fay Wang
>
> The openjpa manual states clearly that a second unmanaged DataSource is
> required for updating sequence table (page 205: 4.2.1. Managed and XA
> DataSources):
> "When using a managed DataSource, you should also configure a second
> unmanaged DataSource that OpenJPA can use to perform tasks that are
> independent of the global transaction. The most common of these tasks is
> updating the sequence table OpenJPA uses to generate unique primary key
> values for your datastore identity objects. Configure the second DataSource
> using the non-jta-data-source persistence.xml element, or OpenJPA's various
> "2" connection properties, such as openjpa.ConnectionFactory2Name or
> openjpa.Connection2DriverName. These properties are outlined in
> Chapter 2, Configuration [161]."
> Openjpa, however, does not this rule when Sequence table is involved. As a
> result, the application hangs when only one datasource is configured. This is
> not very user-friendly. An error message should be thrown when this situation
> is detected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
