I have been running the default configuration of JBoss for a while and am now 
looking at the startguide40.zip with Duke's Bank Application.

This states I must use HSSQL in TCP (server) mode, it was original setup and 
running in localDB (memory) mode.

Now JBoss does not start correctly, as-if the tables are missing, its like 
HSSQL has setup a brand new instance of itself.  My understanding was I was 
simply changing the allowable access methods to the same data not creating a 
new database instance.  There are now both localDB.* and default.* files in the 
data/hypersonic directory.

What should I do ?  shutdown the other instance ?

Migrate the data from one to the other ?  (The .script files are text SQL 
command, and there is no data to really migrate, the localDB.script and 
default.script look similar all but the extra table created in default.script 
for the Duke Bank App).

Keep both instances and change the naming or order the are defined in the file ?

Thanks

Darryl


THEN:
<connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}hypersonic${/}localDB</connection-url>
  | <mbean code="org.jboss.jdbc.HypersonicDatabase"
  |      name="jboss:service=Hypersonic,database=localDB">
  |      <attribute name="Database">localDB</attribute>
  |      <attribute name="InProcessMode">true</attribute>
  |    </mbean>
  | 

NOW:
<connection-url>jdbc:hsqldb:hsql://localhost:1701</connection-url>
  | <mbean code="org.jboss.jdbc.HypersonicDatabase"
  |      name="jboss:service=Hypersonic">
  |      <attribute name="Port">1701</attribute>
  |      <attribute name="Silent">true</attribute>
  |      <attribute name="Database">default</attribute>
  |      <attribute name="Trace">false</attribute>
  |      <attribute name="No_system_exit">true</attribute>
  |    </mbean>
  | <mbean code="org.jboss.jdbc.HypersonicDatabase"
  |      name="jboss:service=Hypersonic,database=localDB">
  |      <attribute name="Database">localDB</attribute>
  |      <attribute name="InProcessMode">true</attribute>
  |    </mbean>


The first error:

anonymous wrote : 17:49:43,970 ERROR [GeneralPurposeDatabasePersistencePlugin] 
Cannot create timer table
  | org.jboss.deployment.DeploymentException: Error while checking if table 
aleady exists TIMERS; - nested throwable: (java.sql.SQLException: Table not 
found:
  | SYSTEM_TABLES in statement [SELECT * FROM SYSTEM_TABLES])
  |         at 
org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.tableExists(SQLUtil.java:1002)
  |         at 
org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.createTableIfNotExists(GeneralPurposeDatabasePersistencePlugin.java:92)
  |         at 
org.jboss.ejb.txtimer.DatabasePersistencePolicy.startService(DatabasePersistencePolicy.java:96)
  | 

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875164#3875164

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875164


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to