[ https://issues.jboss.org/browse/AS7-2611?page=com.atlassian.jira.plugin.s... ] Carlo de Wolf updated AS7-2611: ------------------------------- Priority: Critical (was: Major) Description: I am seeing what looks like a race condition in the CMP tests. It appears that this may be caused by org.jboss.as.cmp.ejbql.Catalog not being synchronized, and if multiple org.jboss.as.cmp.jdbc.JdbcStoreManagerInitService start concurrently concurrent access may result. Not sure if this is the correct diagnosis though. {noformat} 20:16:12,652 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-12) MSC00001: Failed to start service jboss.deployment.unit."cmp-relationship.jar".component.A_OneToMany_Uni_Table_EJB.jdbc.store-manager.RELATIONS: org.jboss.msc.service.StartException in service jboss.deployment.unit."cmp-relationship.jar".component.A_OneToMany_Uni_Table_EJB.jdbc.store-manager.RELATIONS: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] at java.lang.Thread.run(Thread.java:680) [:1.6.0_29] Caused by: java.lang.RuntimeException: Related entity not found: entity=A_OneToMany_Uni_Table_EJB, cmrField=b, relatedEntity=B_OneToMany_Uni_Table_EJB at org.jboss.as.cmp.jdbc.bridge.JDBCCMRFieldBridge.resolveRelationship(JDBCCMRFieldBridge.java:228) at org.jboss.as.cmp.jdbc.bridge.JDBCEntityBridge.resolveRelationships(JDBCEntityBridge.java:257) at org.jboss.as.cmp.jdbc.JDBCStoreManager.resolveRelationships(JDBCStoreManager.java:241) at org.jboss.as.cmp.jdbc.JdbcStoreManagerRelationshipsService.start(JdbcStoreManagerRelationshipsService.java:41) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] ... 3 more {noformat} was: I am seeing what looks like a race condition in the CMP tests. It appears that this may be caused by org.jboss.as.cmp.ejbql.Catalog not being synchronized, and if multiple org.jboss.as.cmp.jdbc.JdbcStoreManagerInitService start concurrently concurrent access may result. Not sure if this is the correct diagnosis though. 20:16:12,652 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-12) MSC00001: Failed to start service jboss.deployment.unit."cmp-relationship.jar".component.A_OneToMany_Uni_Table_EJB.jdbc.store-manager.RELATIONS: org.jboss.msc.service.StartException in service jboss.deployment.unit."cmp-relationship.jar".component.A_OneToMany_Uni_Table_EJB.jdbc.store-manager.RELATIONS: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] at java.lang.Thread.run(Thread.java:680) [:1.6.0_29] Caused by: java.lang.RuntimeException: Related entity not found: entity=A_OneToMany_Uni_Table_EJB, cmrField=b, relatedEntity=B_OneToMany_Uni_Table_EJB at org.jboss.as.cmp.jdbc.bridge.JDBCCMRFieldBridge.resolveRelationship(JDBCCMRFieldBridge.java:228) at org.jboss.as.cmp.jdbc.bridge.JDBCEntityBridge.resolveRelationships(JDBCEntityBridge.java:257) at org.jboss.as.cmp.jdbc.JDBCStoreManager.resolveRelationships(JDBCStoreManager.java:241) at org.jboss.as.cmp.jdbc.JdbcStoreManagerRelationshipsService.start(JdbcStoreManagerRelationshipsService.java:41) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] ... 3 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2611?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-2611: --------------------------------------- Can this be resolved? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2611?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-2611. --------------------------------- Assignee: Stuart Douglas (was: John Bailey) Fix Version/s: 7.1.0.Final Resolution: Done The existing barriers were not enough, the Catalog was having entities being added concurrently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira