Bug 777562 (SOA-65)

Summary: UUID service startup fails when using Oracle database
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: trev <tkirby>
Component: DocumentationAssignee: trev <tkirby>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 IR3   
Target Milestone: ---   
Target Release: 4.2 CR1   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-65
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-16 09:18:39 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:

Description trev 2007-10-24 09:19:55 UTC
Date of First Response: 2007-12-18 15:47:53
Workaround: Workaround Exists
Workaround Description: change the table name in ${CONFIG}/deploy/uuid-key-generator.sar/META-INF/jboss-service.xml. to username.tablename
project_key: SOA

If the UUID service should create the table for UUID generators and in another schema in the same database the table exists then it is false identified as already existing in current user scheme. The workaround is to use table name in jboss-service.xml file fully qualified inluding schema name.
This fact should be stated in the comment of the file or in the documentation.

Comment 1 trev 2007-10-24 09:21:13 UTC
Link: Added: This issue depends JBESB-1127


Comment 2 trev 2007-10-24 09:32:12 UTC
Originally raised in ESB as JBESB-1127 - should be a soa issue 
Comments copied from original


Kurt Stam [23/Oct/07 12:56 PM] Jira, I don't think I understand this jira. Which UUID service is this?


Jiri Pechanec [24/Oct/07 01:45 AM] Hi, it should be probably better to put this issue under SOA project but leave it is as. Check uuid-key-generator.sar/META-INF/jboss-service.xml. There is an attribute named TableName. During the startup this service tries to do select on this table and if it exists in different schema then it succeds (maybe global synonyms or whatever). So it will not create table in current schema and subsequent SQL statements fails. If you will change the table name to username.tablename then this service runs smoothly as the probe select will fail and new table in current schema is created.


Jiri Pechanec [24/Oct/07 04:24 AM] No


Comment 3 trev 2007-10-24 09:32:45 UTC
Link: Removed: This issue depends JBESB-1127 


Comment 4 trev 2007-12-12 14:04:17 UTC
Link: Added: This issue depends JBPAPP-492


Comment 5 trev 2007-12-12 14:05:23 UTC
The issue has been raised in EAP, if they fix it we will inherit the fix.

Comment 6 Mark Little 2007-12-18 20:47:53 UTC
Can you update the Affects field in the EAP issue?

Comment 7 Mark Little 2007-12-22 13:38:47 UTC
Workaround Description: Added: change the table name in ${CONFIG}/deploy/uuid-key-generator.sar/META-INF/jboss-service.xml. to username.tablename
Workaround: Added: [Workaround Exists]


Comment 8 Mark Little 2007-12-22 13:39:16 UTC
Use the workaround for now and push this issue out to whenever JBAPP fixes it.

Comment 9 Mark Little 2008-01-16 09:18:39 UTC
Rejected for the same reason as the linked issue.

Comment 10 Len DiMaggio 2008-06-23 15:10:47 UTC
Link: Added: This issue is a dependency of JBQA-730


Comment 11 Len DiMaggio 2008-06-23 15:12:54 UTC
Link: Removed: This issue is a dependency of JBQA-730 


Comment 12 Len DiMaggio 2008-06-23 15:13:34 UTC
Link: Added: This issue is a dependency of JBQA-1579