[
https://issues.apache.org/jira/browse/LABS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Gianni updated LABS-472:
-------------------------------
Assignee: Simone Gianni
> [database] Concurrency problem in JPA database initialization
> -------------------------------------------------------------
>
> Key: LABS-472
> URL: https://issues.apache.org/jira/browse/LABS-472
> Project: Labs
> Issue Type: Bug
> Components: Magma
> Affects Versions: Current
> Reporter: Simone Gianni
> Assignee: Simone Gianni
> Priority: Critical
> Fix For: Current
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> The problem is evident when more than one thread starts using the database
> during startup. For example, when there are jobs that run concurrently with
> main startup sequence.
> Two different JPA connections are started, and one of the two reports errors
> during initialization.
> A concurrent lock should be present to pause other threads waiting for a
> database connection until the first one is correctly initialized.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: labs-unsubscr...@labs.apache.org
For additional commands, e-mail: labs-h...@labs.apache.org
