Hide Forgot
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.
Link: Added: This issue depends JBESB-1127
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
Link: Removed: This issue depends JBESB-1127
Link: Added: This issue depends JBPAPP-492
The issue has been raised in EAP, if they fix it we will inherit the fix.
Can you update the Affects field in the EAP issue?
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]
Use the workaround for now and push this issue out to whenever JBAPP fixes it.
Rejected for the same reason as the linked issue.
Link: Added: This issue is a dependency of JBQA-730
Link: Removed: This issue is a dependency of JBQA-730
Link: Added: This issue is a dependency of JBQA-1579