Project

General

Profile

MUC chat message duplicates

Vinoth Rajendran
Added over 4 years ago

I am using Tigase 5.2.3 and MUC tigase-muc-2.2.0. My configuration as follows,

--comp-class-1 = tigase.muc.MUCComponent
--comp-class-6 = tigase.muc.MUCComponent
--comp-class-5 = tigase.muc.MUCComponent
--virt-hosts = 192.168.1.94
--user-db-uri = jdbc:mysql://localhost/tigasedb?user=root&password=root
--user-db = mysql
--admins = admin@192.168.1.94
--comp-name-4 = message-archive
--comp-name-3 = proxy
config-type = --gen-config-all
--comp-name-2 = pubsub
--comp-name-6 = conference
--comp-name-5 = channel
--comp-name-1 = muc
--cluster-mode = true
--sm-plugins = +message-archive-xep-0136

# To save group chat message. 
conference/default_room_config/conference#roomconfig_persistentroom=true
muc/default_room_config/muc#roomconfig_persistentroom=true
channel/default_room_config/channel#roomconfig_persistentroom=true

--debug = server, archive
--comp-class-4 = tigase.archive.MessageArchiveComponent
--comp-class-3 = tigase.socks5.Socks5ProxyComponent
--comp-class-2 = tigase.pubsub.PubSubComponent

# To Enabling typing notification
conference/muc-allow-chat-states[B]=true
conference/message-filter-enabled[B]=false

muc/muc-allow-chat-states[B]=true
#muc/message-filter-enabled[B]=false

message-archive/archive-repo-uri=jdbc:mysql://localhost/tigasedb?user=root&password=root

sess-man/plugins-conf/message-archive-xep-0136/required-store-method=message
sess-man/plugins-conf/message-archive-xep-0136/component-jid=message-archive@192.168.1.94

When I enable message filter for MUC to store full stanza message, I got an duplication(i.e Every message rendered two times).

Is there any other way to store full stanza message as soon as no duplication. I am Using Converse.js as client.


Replies (1)

(1)

Added by Wojciech Kapcia TigaseTeam over 4 years ago

Do you have any additional modifications to the server?

Do you experience the issue with other clients?

I've just run a test and it works ok for me:

Send:

<message type="groupchat" to="test@muc.atlantiscity" id="aae6a">
<body>test1</body>
</message>

Got:

<message from="test@muc.atlantiscity/admin" type="groupchat" to="admin@atlantiscity/psi+">
<body>test1</body>
</message>

And another participant as well:

<message from="test@muc.atlantiscity/admin" type="groupchat" to="tig1@atlantiscity/Psi+/1">
<body>test1</body>
</message>

It looks like there may be a compatibility issue with Converse.js client.

Can you try to replicate the issue with the latest nightly release as it contains some compatibility improvements with some clients?

    (1-1/1)