Bug #8554

[MySQL] Sometimes setting version via property doesn't work (without error)

Added by felix liang 3 months ago. Updated 2 months ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Applicable version:
Source Code Disclaimer:


Hi Tigase team

We are Sytac Limted and we are testing tigase to put this to production in very future.
We are using "java -jar tigase-server-7.1.5-b4512.jar" to install tigase 7.1.5 .
And following the guide step by step. No error occurs during the installation.

While i run "./scripts/ start etc/tigase.conf "
From logs/tigase-console.log

Please upgrade database schema now.
Current scheme version is: null, expected: 7.1
Check the schema upgrade guide at the address:
Administration Guide > Tigase Server Schema v7.1 Updates (available locally in docs directory and online
If you have upgraded your schema and you are still
experiencing this problem please contact support at
e-mail address:

I searched the forum and found the following bug very similar to my case.

This bug provide a workaround for this kind of issue ,execute following command should be work.
mysql_upgrade -u root -p --force

After i execute the upper command . It still gives following error.

Here is the i am using now:
--comp-class-1 = tigase.muc.MUCComponent
--virt-hosts =
--auth-db-uri = jdbc:mysql://
--user-db-uri = jdbc:mysql://
--user-db = mysql
--admins =
--comp-name-6 = message-archive
--comp-name-5 = http
--comp-name-4 = stun
--auth-db = tigase-auth
--comp-name-3 = proxy
config-type = --gen-config-def
--comp-name-2 = pubsub
--comp-name-1 = muc
--cluster-mode = false
--sm-plugins = +message-archive-xep-0136,+jabber:iq:auth,+urn:ietf:params:xml:ns:xmpp-sasl,+urn:ietf:params:xml:ns:xmpp-bind,+urn:ietf:params:xml:ns:xmpp-session,+jabber:iq:register,+jabber:iq:roster,+presence,+jabber:iq:privacy,+jabber:iq:version,+,+starttls,+msgoffline,+vcard-temp,+,+jabber:iq:private,+urn:xmpp:ping,+basic-filter,+domain-filter,+pep,+zlib
--comp-class-6 = tigase.archive.MessageArchiveComponent
--debug = server,xmpp.impl,db
--comp-class-5 = tigase.http.HttpMessageReceiver
--comp-class-4 = tigase.stun.StunComponent
--comp-class-3 = tigase.socks5.Socks5ProxyComponent
--comp-class-2 = tigase.pubsub.PubSubComponent

Here is the tigase.conf

ENC="-Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8"
#GC="-XX:+UseBiasedLocking -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:NewRatio=2 -XX:+CMSIncrementalMode -XX:ParallelCMSThreads=2 -XX:-ReduceInitialCardMarks -XX:CMSInitiatingOccupancyFraction=70  -XX:+UseCMSInitiatingOccupancyOnly"
#EX="-XX:+OptimizeStringConcat -XX:+DoEscapeAnalysis -XX:+UseNUMA"

#GC_DEBUG=" -XX:+PrintTenuringDistribution -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -Xloggc:logs/jvm.log -verbose:gc "


#DNS_RESOLVER=" -Dresolver-class=tigase.util.DNSResolverDefault "
#INTERNAL_IP=" -Dtigase-primary-address=hostname.local "
#EXTERNAL_IP=" -Dtigase-secondary-address=hostname "

#PRODUCTION_HEAP_SETTINGS=" -Xms5G -Xmx5G " # heap memory settings must be adjusted on per deployment-base!
TIGASE_OPTIONS=" --property-file etc/ "

Very appreciate if you provide support for this case.

Felix Leung
Business Development Manager

15255_SynTac-Logo2B-B-small.jpg (14.9 KB) 15255_SynTac-Logo2B-B-small.jpg felix liang, 2019-02-04 04:23 AM
tigase.log.0 (144 KB) tigase.log.0 felix liang, 2019-02-04 04:23 AM
tigase-console.log (51.5 KB) tigase-console.log felix liang, 2019-02-04 04:23 AM

Associated revisions

Revision 7a88302a (diff)
Added by W Administrator 2 months ago

#8554 force characterEncoding also on actuall the connection string used to access database and no only on the example configuration


#1 Updated by Wojciech Kapcia TigaseTeam 3 months ago

  • Description updated (diff)
  • Status changed from New to In Progress
  • Assignee changed from Wojciech Kapcia to felix liang

which MySQL version do you use?

Could you try to execute following queries in your database:

select TigGetDBProperty('schema-version');

select * from tig_pairs, tig_users where (user_id = 'db-properties') AND (tig_pairs.uid = tig_users.uid);

#2 Updated by Wojciech Kapcia TigaseTeam 2 months ago

  • Subject changed from !!!!NOT WORKING !!!Solution of Bug #6753: update schema problem - Tigase XMPP Server - Tigase Projects to [MySQL] Sometimes setting version via property doesn't work (without error)
  • Assignee changed from felix liang to Wojciech Kapcia

I reproduced the issue locally - I'm continuing investigation.

#3 Updated by Wojciech Kapcia TigaseTeam 2 months ago

  • Tracker changed from Support to Bug
  • Project changed from Support to Tigase XMPP Server
  • Status changed from In Progress to Resolved
  • Target version set to tigase-server-7.1.6
  • % Done changed from 0 to 100
  • Applicable version set to 7.1.3
  • Source Code Disclaimer set to No
  • Database n/a added

DBSchemaLoader was setting character encoding in example configuration string but not in the actual jdbc urls.

#4 Updated by Wojciech Kapcia TigaseTeam 2 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF