Bug 779307 (SOA-1695)

Summary: jUDDI database initialization fails on Oracle and db2 - not an issue for PostgreSQL
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Jiri Pechanec <jpechane>
Component: JBossESB, Configuration, DeploymentAssignee: Julian Coleman <jcoleman>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.0.0 ER5   
Target Milestone: ---   
Target Release: 5.0.0 GA, 5.0.0 ER7   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1695
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-29 07:46:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jiri Pechanec 2009-12-09 07:22:32 UTC 
Date of First Response: 2009-12-10 11:15:15
project_key: SOA

jUDDI 3 uses Hibernate to access db. During server startup it tries to update db schema to conform mapping files. Unfortunately on Oracle if tables with the same name exists in an other schema then jUDDI thinks that db is correctly initialized and tables are not created.

To fix this issue it is necessary to use hibernate options hibernate.default_schema and/or hibernate.default_catalog in persistence.xml file. This can cuase problems with other databases.

I have tried to change hibernate.hbm2ddl.auto from update to create and issue has disappeared. Moreover this approach is better aligned with other db components using static sql files - no schema change is done inadvertently.
Comment 1 Julian Coleman 2009-12-10 16:15:15 UTC 
SOA-1599 is also a symptom of visibility across multiple schemas.
Comment 2 Julian Coleman 2009-12-10 16:15:15 UTC 
Link: Added: This issue is related to SOA-1599
Comment 3 Julian Coleman 2009-12-21 16:27:20 UTC 
This seems to be more a database setup problem, where multiple schemas are visible.
Changing the schema visibility in the database would fix this.
Comment 4 Lukáš Petrovický 2010-01-05 11:28:22 UTC 
hbm2ddl.auto should never carry the "update" value in the first place - it doesn't properly create indices. For more information, see http://www.hibernate.org/119.html#A10 and HHH-1012 (fixed only recently).
Comment 5 Kevin Conner 2010-01-05 12:01:52 UTC 
Link: Added: This issue depends JBESB-3097
Comment 6 Kevin Conner 2010-01-05 12:03:02 UTC 
Will also modify our base one in case that makes your job easier
Comment 7 Kevin Conner 2010-01-05 12:51:39 UTC 
ESB configuration has been changed, will be in next commit.
Comment 8 Julian Coleman 2010-01-18 14:53:00 UTC 
Resolving this, as the ESB JIRA (JBESB-3097) has been resolved.
Comment 9 Jiri Pechanec 2010-01-29 07:46:37 UTC 
Verified in ER7