[
https://issues.jboss.org/browse/AS7-5395?page=com.atlassian.jira.plugin.s...
]
Eduardo Martins commented on AS7-5395:
--------------------------------------
It turns out that JDBCStartCommand (what creates the tables) is one per CMP entity and, in
a single deployment, each one created may run in a different MSC thread. Then
JDBCStartCommand does not creates only the entity table, it also creates (if does not
exist) every relationship table, so there is a chance that multiple JDBCStartCommands try
to create same relationship table, and when that happen the deployment fails, as above. It
is very possible that it was never an H2 issue, since for every record I have of test
failures, the failure was always on the creation of a relationship table.
Intermittent Testsuite: CMP Relationship Tests
----------------------------------------------
Key: AS7-5395
URL:
https://issues.jboss.org/browse/AS7-5395
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.1.2.Final (EAP)
Reporter: Eduardo Martins
Assignee: Eduardo Martins
Fix For: 7.1.2.Final (EAP)
CMP tests fail sometimes, this is due to an H2 behavior where dropping a table (done by a
CMP module processor on undeploy) may be incomplete when a new deploy starts, and needs
same tables.
In concrete, the deploy code will not find the table(s) on the DB metadata, tries to
create and this fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira