Robert, I think this is not a bug in Tigase but rather a problem with your installation and incorrect libraries version used for your Tigase server.

Wojciech will provide you more details and instructions on how to resolve this.

Rober, can you share:

• whole command you used to initialize schema update?

• complete output (especially full stacktrace)?

Can you try adding &useUnicode=true&characterEncoding=UTF-8 to your JDBC connection strings?

Thanks Wojciech, maybe I've found already the problem, a very few minutes ago. I've already tried to add &useUnicode=true&characterEncoding=UTF-8 to the JDBC connection.

I've found out something different. The collation of my MySQL database seems to have been changed a little bit after an update performed by the hoster.

I have had the problem with the following settings:

mysql> show variables like 'col%';
+----------------------+-----------------+
| Variable_name        | Value           |
+----------------------+-----------------+
| collation_connection | utf8_general_ci |
| collation_database   | utf8_unicode_ci |
| collation_server     | utf8_unicode_ci |
+----------------------+-----------------+
3 rows in set (0.00 sec)

I've changed to:

mysql> show variables like 'col%';
+----------------------+-----------------+
| Variable_name        | Value           |
+----------------------+-----------------+
| collation_connection | utf8_unicode_ci |
| collation_database   | utf8_unicode_ci |
| collation_server     | utf8_unicode_ci |
+----------------------+-----------------+
3 rows in set (0.00 sec)

Nevertheless, the problem still occurred.

Then I tried to built up the tigase from the scratch, the problem still occurred.

Finally I've tried to change everything to utf8_general_ci. And now it seems to be working fine!

Robert N wrote:

Finally I've tried to change everything to utf8_general_ci. And now it seems to be working fine!

Closing then.