Bug 778433 (SOA-915) - Schema tool broken for non-clustered configs
Summary: Schema tool broken for non-clustered configs
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-915
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Tooling
Version: 4.3 IR5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.3 CR1
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-06 05:30 UTC by Jiri Pechanec
Modified: 2008-10-20 12:15 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-20 12:15:16 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-915 0 None None None Never

Description Jiri Pechanec 2008-10-06 05:30:42 UTC
Date of First Response: 2008-10-08 05:29:18
project_key: SOA

The schema tool uses template to set JBoss Messaging configuration *-persistence-service.xml. These files are prepared for clustered configs - see JGroups definitions inside the files.
This has two consequences
1) It will suddenly switch default config of embedded server from non-clustered to clustered
2) The standalone server will not start as JGroups are not present there and thus the config is invalid

Comment 1 Julian Coleman 2008-10-08 09:29:18 UTC
Fixed in revision 2060 of:
  schema/jms/clustered-mysql-persistence-service.xml
  schema/jms/clustered-oracle-persistence-service.xml
  schema/jms/clustered-postgresql-persistence-service.xml
  schema/jms/db2-persistence-service.xml
  schema/jms/mssql-persistence-service.xml
  schema/jms/mysql-persistence-service.xml
  schema/jms/ndb-persistence-service.xml
  schema/jms/null-persistence-service.xml
  schema/jms/oracle-persistence-service.xml
  schema/jms/oracle10g-persistence-service.xml
  schema/jms/oracle9i-persistence-service.xml
  schema/jms/postgresql-persistence-service.xml
  schema/jms/sybase-persistence-service.xml
  schema/tool/esb/build.xml
  schema/tool/esb/db2/template/db2-persistence-service.xml
  schema/tool/esb/mssql/template/mssql-persistence-service.xml
  schema/tool/esb/mysql/template/mysql-persistence-service.xml
  schema/tool/esb/oracle10g/template/oracle-persistence-service.xml
  schema/tool/esb/oracle9i/template/oracle-persistence-service.xml
  schema/tool/esb/postgresql/template/postgresql-persistence-service.xml
  schema/tool/esb/sybase/template/sybase-persistence-service.xml
along with SOA-757.

Commit message:
  Add clustered-* versions of
    mysql-persistence-service.xml
    oracle-persistence-service.xml
    postgresql-persistence-service.xml
  for use with `production' and `all' configurations.  Modify the schema tool
  to prepend "clustered-" for these deploys.  The clustered-* versions are the
  same as the original files, the original files now contain non-clustered
  configurations.  Note, that only the databases supported by the schema tool
  (mysql, oracle and postgresql) have been changed.

  Delete *-persistence-service.xml files that are duplicates (the ones in
  tool/esb/*/template/), or not used (oracle9i-* and oracle10g-*).

  Add POPULATE.TABLES.15 line for those files that were missing it.

  Fixes JIRA's SOA-757 and SOA-915.

  Thanks to Jirka for testing the fix for SOA-915.



Comment 2 Jiri Pechanec 2008-10-20 12:15:16 UTC
Verified in CR1


Note You need to log in before you can comment on or make changes to this bug.