tigase5.2.3 using mysql5.6 Error

Problem:

1. The user cannot log in after installing the console parameter of jar package, and the log file of Tigase-console.log appears

[Hostnames] Userrepositorymdimpl.getdata () warning:couldn ' t obtain user repository for Domain:vhost-manager, not even default O ne!

2, in MySQL view Tigase Library, found that the Tig_users table is missing. The complete table is as follows

+--------------------------+| tables_in_tigasedb       |+------------- -------------+| short_news                | |  tig_nodes                 | |  tig_pairs                 | |  tig_pubsub_affiliations  | |  tig_pubsub_items         | |  tig_pubsub_jids          | |  tig_pubsub_nodes         | |  tig_pubsub_service_jids  | |  tig_pubsub_subscriptions | |  tig_socks5_connections   | |  tig_socks5_users         | |  tig_users                | |  xmpp_stanza              |+------- -------------------+

3. If an error occurs when importing with Database/mysql-schema-5-1.sql

MySQL ERROR 1071 (42000): Specified key was too long; Max key length is 767 bytes

4, using the scripts/db-create-mysql.sh script in the tigase-server-5.2.3-b3470-dist-max.tar.gz package to create a database appears

MySQL ERROR 1071 (42000): Specified key was too long; Max key length is 767 bytes

Reason:

This was related to the changes in MySQL 5.6 and new limits.
With the release of MySQL 5.6 There were a few changes to the defaults used by the database server mostly related to Defau LT engine which entails change in defaults regarding length of index key limits. This version switched from MyISAM to InnoDB (v. 5.1:default-storage-engine vs 5.6:default-storage-engine) and then Limit s on InnoDB Tables for 5.1 and 5.6. The result in default configuration is the limitation of 767 bytes for index key prefix which are not met by Tigase schema Because it defaults to using UTF8 for storage and while we define key length as 765 characters, because of using Unicode ( In case of MySQL this translates to 3-4bytes per character) we cross the maximum key length limitation.

Workaround:

Add the following to the MySQL configuration file (typically under Linux in/etc/my.cnf):

Innodb_large_prefix=trueinnodb_file_format=barracudainnodb_file_per_table=true

After you restart MySQL, reinstall or import the SQL file.

Reference: https://projects.tigase.org/boards/15/topics/3244

This article is from "Busy Tam Xiao Zhu" blog, please make sure to keep this source http://soarwilldo.blog.51cto.com/5520138/1586238

tigase5.2.3 using mysql5.6 Error