Project

General

Profile

Tigase server V5.2.0 rc1 cluster with acs did not work well

ken chen
Added over 5 years ago

Hi guys,

I deployed two cluster nodes using tigase server V5.2.0 rc1 with acs, but

them did not work together:

user A and user B were friends each other. A logined in node1,B logined in

node2,but them displayed offline each other. then I checked the

database,there was a table named cluster_nodes with two recorders, and I

found some errors in tigase-console.log:

2013-12-05 13:06:20.133 [main] SimpleCache.()

WARNING: Tigase cache turned off.

Loading plugin: message-carbons=4 ... , version: 5.2.0-rc1-b3372/c86055df

(2013-11-21/13:29:44)

Loading plugin: mobile_v2=4 ... , version: 5.2.0-rc1-b3372/c86055df

(2013-11-21/13:29:44)

Loading component: sess-man :: componentInfo{Title=Tigase XMPP Server,

Version=5.2.0-rc1-b3372/c86055df (2013-11-21/13:29:44),

Class=tigase.cluster.SessionManagerClustered,

componentData={ClusteringStrategy=class

tigase.cluster.strategy.OnlineUsersCachingStrategy}}

Loading component: ws2s :: componentInfo{Title=Tigase XMPP Server,

Version=5.2.0-rc1-b3372/c86055df (2013-11-21/13:29:44),

Class=tigase.cluster.WebSocketClientConnectionClustered}

2013-12-05 13:06:21.001 [main] ConfigurationCache.store()

WARNING: Dumping server configuration to: etc/config-dump.properties

2013-12-05 13:06:40.410 [ConnectionOpenThread] SocketThread.()

WARNING: 17 socketReadThreads started.

2013-12-05 13:06:40.429 [ConnectionOpenThread] SocketThread.()

WARNING: 17 socketWriteThreads started.

2013-12-05 13:06:40.447 [pool-12-thread-3]

ClusterConnectionManager.processHandshake() WARNING: Handshaking password

doesn't match, disconnecting...

2013-12-05 13:06:40.448 [pool-12-thread-4]

ClusterConnectionManager.processHandshake() WARNING: Handshaking password

doesn't match, disconnecting...

2013-12-05 13:09:33.779 [in_5-sess-man]

OnlineUsersCachingStrategy.handleLocalPacket() WARNING: Problem with

broadcast user presence for: user_jid=demo@mydomain/Pandion, packets=10,

connectioId=c2s@node1-server/192.168.1.6_5222_192.168.1.9_1290,

domain=xmpp.org.cn, authState=AUTHORIZED, isAnon=false

java.lang.NullPointerException

at tigase.server.Packet.packetInstance(Packet.java:243)

at

tigase.cluster.strategy.OnlineUsersCachingStrategy.handleLocalPacket(Unknown

Source)

at

tigase.cluster.SessionManagerClustered.handleLocalPacket(SessionManagerClustered.java:157)

at

tigase.server.xmppsession.SessionManager.processPacket(SessionManager.java:1861)

at

tigase.cluster.SessionManagerClustered.processPacket(SessionManagerClustered.java:323)

at

tigase.cluster.SessionManagerClustered.processPacket(SessionManagerClustered.java:302)

at

tigase.server.AbstractMessageReceiver$QueueListener.run(AbstractMessageReceiver.java:1475)

Could you help me,thanks.


Replies (6)

Added by Wojciech Kapcia TigaseTeam over 5 years ago

From which node the excerpt is? Could you share full configuration?

Warning about failed cluster handshaking stem from the fact that we are using dynamic nodes discovery with random passwords (stored in mentioned table) thus before node fully start up an old password may be used.

Added by ken chen over 5 years ago

thanks for your reply.

node1:

config-type = --gen-config-def

--cluster-mode = true

--sm-cluster-strategy-class=tigase.cluster.strategy.OnlineUsersCachingStrategy

--debug = server

--user-db = mysql

--admins = admin@xmpp.org.cn

--user-db-uri = jdbc:mysql://192.168.1.2/tigase_db?user=root&password=password

--virt-hosts = xmpp.org.cn

--sm-plugins = +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:privacy,+jabber:iq:version,+starttls,+amp,+vcard-temp,+jabber:iq:private,+urn:xmpp:ping,-pep,+mobile_v2,+jabber:iq:roster,+presence,-message,-msgoffline,-http://jabber.org/protocol/commands,-http://jabber.org/protocol/stats,-basic-filter,-domain-filter,-zlib

node2:

config-type = --gen-config-def

--cluster-mode = true

--sm-cluster-strategy-class=tigase.cluster.strategy.OnlineUsersCachingStrategy

--debug = server

--user-db = mysql

--admins = admin@xmpp.org.cn

--user-db-uri = jdbc:mysql://192.168.1.2/tigase_db?user=root&password=password

--virt-hosts = xmpp.org.cn

--sm-plugins = +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:privacy,+jabber:iq:version,+starttls,+amp,+vcard-temp,+jabber:iq:private,+urn:xmpp:ping,-pep,+mobile_v2,+jabber:iq:roster,+presence,-message,-msgoffline,-http://jabber.org/protocol/commands,-http://jabber.org/protocol/stats,-basic-filter,-domain-filter,-zlib

Added by ken chen over 5 years ago

that's all, thanks.

Added by Wojciech Kapcia TigaseTeam over 5 years ago

There was a bug in ACS component which was fixed after RC1 release; please try ACS component from latest nightly and check if it's working for you.

Added by ken chen over 5 years ago

Thanks, It worked well with tigase server V5.2.0 rc1 finally, but it was not yet compatible with tigase server V5.1.5, Where can I get an acs version compatible with tigase server V5.1.5? Thank you very much.

Added by Wojciech Kapcia TigaseTeam over 5 years ago

For the version 5.1.5 we offered only licenced version of ACS thus lack of it's publicly available distribution.

    (1-6/6)