Hello,
I am trying to setup the Hermes 2 Messaging Gateway. However the install is failing with the following errors:
[sql] Failed to execute: DROP TABLE message
[sql] com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown table 'message'
[sql] Failed to execute: DROP TABLE repository
[sql] com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown table 'repository'
[sql] Failed to execute: DROP TABLE outbox
[sql] com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown table 'outbox'
[sql] Failed to execute: DROP TABLE inbox
[sql] com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown table 'inbox'
[sql] Failed to execute: DROP TABLE partnership
[sql] com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown table 'partnership'
[sql] Failed to execute: CREATE TABLE message ( message_id varchar(255), message_box varchar(255), message_type varchar(255), from_party_id varchar(255), from_party_role varchar(255), to_party_id varchar(255), to_party_role varchar(255), cpa_id varchar(255), service varchar(255), action varchar(255), conv_id varchar(255), ref_to_message_id varchar(255), sync_reply varchar(5), dup_elimination varchar(5), ack_requested varchar(5), ack_sign_requested varchar(5), sequence_no integer, sequence_status integer, sequence_group integer, time_to_live timestamp null default null, time_stamp timestamp null default null, timeout_time_stamp timestamp null default null, status varchar(2), status_description varchar(4000), PRIMARY KEY (message_id, message_box) )TYPE= INNODB
BUILD FAILED
C:\Users\GARY~1.HAL\AppData\Local\Temp\10\antinstall\build.xml:395: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE= INNODB' at line 1
Total time: 4 seconds
I am using the following old versions of software so I can at least get the setup succesfully completed before attempting to upgrade to new versions of the products :
Tomcat 5.5.26
Java SDK 5.0_22
My SQL 5.5.41
I would be very grateful if anybody could poiny me in the direction of what needs to be changed to resolve the SQL error?
Thanks.
Gary Hall.