After installation, I modified the BASServer.props file to include the 'root' password as per the installation instructions. Before starting the Aware IM Control Panel, I ensured that the 2 Catalogs (bsadb, and basdbtest) are not present in MySql. JBoss and Tomcat activation finish successfully, however, the following error (exception) is generated for the Aware IM Server:
.
.
.
Unable to connect to the existing database Could not establish connection with the data base Unknown database 'basdb'
Creating main data base...
Database created.
The setting for database 'max_allowed_packet' variable is not sufficient. Setting the value to 16M
com.bas.basserver.bsmanager.StartupException: The required database table BAS_IDGEN does not exist or is corrupt.
Please either recover the table manually or drop Aware IM databases and re-start the Aware IM server
at com.bas.basserver.persistence.EntityIdGenerator.initialise(Unknown Source)
at com.bas.basserver.persistence.EntityDBPersister.initialise(Unknown Source)
at com.bas.basserver.persistence.PersistenceManager$a.a(Unknown Source)
at com.bas.basserver.persistence.PersistenceManager$a.if(Unknown Source)
at com.bas.basserver.persistence.PersistenceManager.initialise(Unknown Source)
at com.bas.basserver.bsmanager.e.a(Unknown Source)
at com.bas.basserver.bsmanager.n.if(Unknown Source)
at com.bas.basserver.bsmanager.i$c.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Exception for persister Database
Unable to connect to the existing testing database Could not establish connection with the data base Unknown database 'basdbtest'
Creating database for testing...
Database created.
The setting for database 'max_allowed_packet' variable is not sufficient. Setting the value to 16M
com.bas.basserver.bsmanager.StartupException: The required database table BAS_IDGEN does not exist or is corrupt.
Please either recover the table manually or drop Aware IM databases and re-start the Aware IM server
at com.bas.basserver.persistence.EntityIdGenerator.initialise(Unknown Source)
at com.bas.basserver.persistence.EntityDBPersister.initialise(Unknown Source)
at com.bas.basserver.persistence.PersistenceManager$a.a(Unknown Source)
at com.bas.basserver.persistence.PersistenceManager$a.if(Unknown Source)
at com.bas.basserver.persistence.PersistenceManager.initialise(Unknown Source)
at com.bas.basserver.bsmanager.e.a(Unknown Source)
at com.bas.basserver.bsmanager.n.if(Unknown Source)
at com.bas.basserver.bsmanager.i$c.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Exception for persister Database
log4j:ERROR Could not find value for key log4j.appender.A_TEST
log4j:ERROR Could not instantiate appender named "A_TEST".
'PublicHolidays' property not found in property file
Creating database tables...
Dropping database tables...
2008-11-24 16:18:50,736 ERROR -Error rolling back initialisation of database tables
Aware IM Server startup error Unable to initialise the database tables due to the following exception com.bas.basserver.persistence.PersistenceException Error creating database tables. SQL Exception thrown Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT' exiting...
com.bas.basserver.bsmanager.StartupException: Unable to initialise the database tables due to the following exception com.bas.basserver.persistence.PersistenceException Error creating database tables. SQL Exception thrown Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
at com.bas.basserver.bsmanager.e.a(Unknown Source)
at com.bas.basserver.bsmanager.e.a(Unknown Source)
at com.bas.basserver.bsmanager.n.if(Unknown Source)
at com.bas.basserver.bsmanager.i$c.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
