Did you turn on external connections to the hypersonic database as the tutorial described?
Yes, if you are referring to the instructions in section 220.127.116.11 Enabling the HSQL MBean and TCP/IP Connections. After the mods my jboss-build.xml file looks as follows:
<!-- The jndi name of the DataSource, it is prefixed with java:/ -->
<!-- Datasources are not available outside the virtual machine -->
<!-- for tcp connection, allowing other processes to use the hsqldb
database. This requires the org.jboss.jdbc.HypersonicDatabase mbean. -->
<!-- for totally in-memory db, not saved when jboss stops.
The org.jboss.jdbc.HypersonicDatabase mbean necessary
<!-- for in-process persistent db, saved when jboss stops. The
org.jboss.jdbc.HypersonicDatabase mbean is not necessary for properly db shutdown
I have found the cause. The documentation says "Open the hsqldb-ds.xml file which you’ll find in the deploy directory and which sets up the default datasource". The problem ws there are 2 deploy directories - one under ~all and another under ~default. Both these locations have a copy of the hsqldb-ds.xml file. The mods outlined in the manual have to be done in both files. I had made the mods to the one under all/deply only initially. After I made the mods to the file in default/deploy directory and restarterd the JBoss server, the db-create-table etc started working again.
The mods do not need to be performed in both locations.
Each folder under the server folder is a different isolated JBoss configuration, if you start JBoss from the run script and do not pass in any arguments the default configuration will be started i.e The files under default will be used, the all configuration will not be touched.
If you execute the run command as 'run -c all' the all configuration will be used and the files under default will not be touched.
Thank you very much. That is a useful piece of information. I must have missed reading that part in the manual.