Project

General

Profile

Recieve a message twice

Behnam Hatami
Added over 3 years ago

Hi every body,

I have a tigase server with below configuration.

--cluster-mode = false

--test = false
--debug = server,xmpp.impl


--virt-hosts = X
--admins = admin@X

#--monitoring=jmx:9050
--stats-history = 480,300

--stats-archiv=tigase.stats.CounterDataFileLogger:stats-file-logger:300
stats/stats-archiv/stats-file-logger/stats-directory=logs/server_statistics
stats/stats-archiv/stats-file-logger/stats-filename=stat
stats/stats-archiv/stats-file-logger/stats-unixtime=false
stats/stats-archiv/stats-file-logger/stats-datetime=true
stats/stats-archiv/stats-file-logger/stats-datetime-format=HH:mm:ss
stats/stats-archiv/stats-file-logger/stats-level=FINE

message-router/components/msg-receivers/ws2s.active[B]=false
message-router/components/msg-receivers/bosh.active[B]=false

--vhost-anonymous-enabled = false
--cm-see-other-host = none

# --user-db-uri = jdbc:mysql://localhost/tigase?user=tigase&password=tigase
# --user-db = mysql

--user-db-uri = jdbc:postgresql://localhost/tigase?user=tigase&password=tigase
--user-db = pgsql

basic-conf/logging/java.util.logging.FileHandler.pattern = /var/log/tigase/tigase.log
basic-conf/config-dump-file = /etc/tigase/config-dump.properties

c2s/processors[s]=urn:xmpp:sm:3
c2s/xmpp-ack[B]=true
#c2s/watchdog_delay[L]=30000
#c2s/watchdog_timeout[L]=60000
#c2s/watchdog_ping_type=xmpp

--domain-filter-policy=OWN
--new-connections-throttling = 5222:500

--sm-plugins = +jabber:iq:last,+message-carbons,-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,+http://jabber.org/protocol/stats,+starttls,+vcard-temp,+http://jabber.org/protocol/commands,+jabber:iq:private,+urn:xmpp:ping,+basic-filter,+domain-filter,-pep,-zlib,+amp,-message,-msgoffline,+urn:xmpp:blocking
--amp-security-level=PERFORMANCE

sess-man/plugins-conf/amp/msg-offline = true
sess-man/plugins-conf/jabber\:iq\:roster/auto-authorize = true
sess-man/plugins-conf/presence/auto-authorize = true

sess-man/plugins-conf/amp/store-limit=100000
amp/store-limit[S]=100000

--comp-name-1 = proxy
--comp-class-1 = tigase.socks5.Socks5ProxyComponent

When I send a message from client A to client B, I see it in client B.

07-15 15:47:35.955   16939-7619/ D/SMACK﹕ RECV (28): <message id="Z78GXgMmb7OH3rl16boGmkjkq3m77J" type="chat" to="yo9qxkq61zh5@X" xmlns="jabber:client" from="vv71lfjrgcwu@X/ba1dd717b6ef5a26"><body>XXX</body><thread>_oMVsOplU</thread><active xmlns="http://jabber.org/protocol/chatstates"/><request xmlns="urn:xmpp:receipts"/></message>
07-15 15:47:35.989   16939-7618/ D/SMACK﹕ SENT (28): <message to='vv71lfjrgcwu@X/ba1dd717b6ef5a26' id='3289F-475' type='chat'><received xmlns='urn:xmpp:receipts' id='Z78GXgMmb7OH3rl16boGmkjkq3m77J'/></message>
07-15 15:47:35.992   16939-7618/ D/SMACK﹕ SENT (28): <r xmlns='urn:xmpp:sm:3'/>
07-15 15:47:36.152   16939-7619/ D/SMACK﹕ RECV (28): <a xmlns='urn:xmpp:sm:3' h='10'/>
then I go offline in client B and go online again, I receive the same message again from offline store now
07-15 15:50:52.275  16939-14318/ D/SMACK﹕ RECV (31): <message id="Z78GXgMmb7OH3rl16boGmkjkq3m77J" type="chat" to="yo9qxkq61zh5@X" xmlns="jabber:client" from="vv71lfjrgcwu@X/ba1dd717b6ef5a26"><body>XXX</body><thread>_oMVsOplU</thread><active xmlns="http://jabber.org/protocol/chatstates"/><request xmlns="urn:xmpp:receipts"/><delay stamp="2015-07-15T11:20:28.147Z" xmlns="urn:xmpp:delay" from="X"/><delay stamp="2015-07-15T11:20:28.202Z" xmlns="urn:xmpp:delay" from="X">Offline Storage - X</delay></message>

Is it a server side bug?


Replies (1)

Added by Wojciech Kapcia TigaseTeam over 3 years ago

Most likely Stream Management either haven't confirmed this packet or the confirmation hasn't reached the server so the packet was stored to the offline repository and then delivered upon re-connection.

    (1-1/1)