Hide Forgot
Affects: Release Notes Date of First Response: 2008-05-30 01:10:27 project_key: SOA We need to document the fact that, if a user decides to switch the SOA-P DB, they will have to delete the datasource files from the original DB server. If they don't do this before running the schema tool for a second time, the resulting server configuration will fail to start - this exception is raised: 2008-04-09 15:29:37,728 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/opt/CP01/jboss-soa-p.4.2.0/jboss-as/server/production/deploy/oracle-ds.xml org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.jca:service=LocalTxCM,name=DefaultDS The problem is that the tool does not delete the -ds.xml file for the previously defined DB server: [ldimaggi@ldimaggi log]$ ls /opt/CP01/jboss-soa-p.4.2.0/jboss-as/server/production/deploy/*ds* /opt/CP01/jboss-soa-p.4.2.0/jboss-as/server/production/deploy/hajndi-jms-ds.xml /opt/CP01/jboss-soa-p.4.2.0/jboss-as/server/production/deploy/management-ds.xml /opt/CP01/jboss-soa-p.4.2.0/jboss-as/server/production/deploy/mysql-ds.xml /opt/CP01/jboss-soa-p.4.2.0/jboss-as/server/production/deploy/oracle-ds.xml Interestingly, the error occurs only after some DB tables have been created - it fails on the HILOSEQUENCES table. mysql> show tables; +----------------------+ | Tables_in_soaesb1_db | +----------------------+ | HILOSEQUENCES | | JBM_COUNTER | | JBM_DUAL | | JBM_MSG | | JBM_MSG_REF | | JBM_ROLE | | JBM_TX | | JBM_USER | | TIMERS | +----------------------+ 9 rows in set (0.00 sec) This is also a feature request - at present - the tool assumes that the out-of-the-box confguration oh HSQLDB is present. [ldimaggi@ldimaggi CP01]$ ls /opt/CP01/jboss-soa-p.4.2.0/jboss-as/server/production/deploy/*ds* /opt/CP01/jboss-soa-p.4.2.0/jboss-as/server/production/deploy/hajndi-jms-ds.xml /opt/CP01/jboss-soa-p.4.2.0/jboss-as/server/production/deploy/hsqldb-ds.xml /opt/CP01/jboss-soa-p.4.2.0/jboss-as/server/production/deploy/management-ds.xml /opt/CP01/jboss-soa-p.4.2.0/jboss-as/tools/schema [ldimaggi@ldimaggi schema]$ grep hsqldb * build.xml build.xml: <include name="hsqldb-ds.xml"/> build.xml: <include name="jboss-messaging.sar/hsqldb-persistence-service.xml"/> build.xml: <include name="jboss-messaging.sar/clustered-hsqldb-persistence-service.xml"/> build.xml: <reconfigure file="${target.dir}/deploy/jbossesb.sar/esb.juddi.xml" old="juddi-sql/hsqldb/" build.xml: <reconfigure file="${target.dir}/deploy/jbpm.esb/jbpm-service.xml" old="hsqldb.sql" build.xml: <reconfigure file="${target.dir}/deploy/jbossesb.esb/jbossesb-service.xml" old="message-store-sql/hsqldb/" build.xml: <reconfigure file="${target.dir}/deploy/jbossesb.sar/esb.juddi.xml" old="juddi-sql/hsqldb/" build.xml: <reconfigure file="${target.dir}/deploy/jbpm.esb/jbpm-service.xml" old="hsqldb.sql" build.xml: <include name="hsqldb-ds.xml"/> build.xml: <include name="jboss-messaging.sar/hsqldb-persistence-service.xml"/> build.xml: <include name="jboss-messaging.sar/clustered-hsqldb-persistence-service.xml"/> build.xml: <reconfigure file="${target.dir}/deploy/jbossesb.sar/esb.juddi.xml" old="juddi-sql/hsqldb/" build.xml: <reconfigure file="${target.dir}/deploy/jbpm.esb/jbpm-service.xml" old="hsqldb.sql" build.xml: <reconfigure file="${target.dir}/deploy/jbossesb.esb/jbossesb-service.xml" old="message-store-sql/hsqldb/" build.xml: <reconfigure file="${target.dir}/deploy/jbossesb.sar/esb.juddi.xml" old="juddi-sql/hsqldb/" build.xml: <reconfigure file="${target.dir}/deploy/jbpm.esb/jbpm-service.xml" old="hsqldb.sql"
https://engineering.redhat.com/docbot/en-US/JBoss_SOA_Platform/4.2/html/SOA_Getting_Started_Guide/SOA_Getting_Started_Guide-Post_Installation_Testing_and_Starting.html#id3012939 "In the <install-directory>/jboss-as/tools/schema directory you will find a set of scripts that will reconfigure the main components of the platform to use the supported database of your choice. These scripts expect the platform to be in the out-of-the-box configuration. If you wish to change the database configuration a second time you must first delete the deployed -ds.xml file for the datasource that you previously configured. This file is found in the server/production/deploy directory."
This solution is not good enough. Unfortunately not only the new files are created but also in other files the string hsqldb is searched and then replaced by the new database - typically location of sql scripts. Thus even after this operation the reconfiguration will not work Exmaples of such files jbossesb.sar/esb.juddi.xml jbpm.esb/jbpm-service.xml jbossesb.esb/jbossesb-service.xml And in console tool console/management-esb/db.properties
Release noted: "The Getting Started Guide describes post-installation configuration of the platform databases using included scripts. These scripts expect the platform to be in the out-of-the-box, unmodified configuration. They will not work a second time."
Link: Added: This issue related SOA-612
This is now fixed. However, the caveat is that if the person INITIALLY manually modified the config files, they will be unable to use the schema tool at a later date. If they initially used the schema tool to configure the database, they will be able to re-configure using the script after the fact.
Link: Added: This issue related SOA-695
Link: Added: This issue related SOA-860
Clarification required for documentation: "if the person INITIALLY manually modified the config files, they will be unable to use the schema tool at a later date. " what config files are being refered to here?
Verified in GA