Project

General

Profile

tigase lost message when client disconnect network

xiaotu ju
Added over 4 years ago

tigage server lost message when client disconnect from network, tigase not store message as offline-msg,when client login again,the message lost


Replies (8)

Added by Natale Vinto over 4 years ago

Hi,

tigase stores messages by AMP default plugin if users disconnects correctly announcing its unavailability, otherwise it tries to send to a broken socket the message and it is lost if any shrewdness is not taken.

Then, you should write your tigase version and your init.properties in order to understand if it is your misconfiguration issue or just the behaviour just described.

Bye

Added by xiaotu ju over 4 years ago

tigase version is lastet 5.3.0 snapshot ,checkout from repository.

now psi receive msg when network disconnect ,but tigase mobile android can't receive any message when network disconnect

here is init config

config-type=--gen-config-def

--admins=admin@liuzh-vh

--virt-hosts = liuzh-vh

--debug=server

--user-db=mysql

--user-db-uri=jdbc:mysql://localhost:3306/tigasedb?user=tigase_user&password=tigase_pass&useUnicode=true&characterEncoding=UTF-8&autoCreateUser=true

--monitoring=jmx:9050,http:9080,snmp:9060

c2s/processors[s]=urn:xmpp:sm:3

--comp-name-1= muc

--comp-class-1= tigase.muc.MUCComponent

--comp-name-2=message-archive

--comp-class-2=tigase.archive.MessageArchiveComponent

--comp-name-3 = test

--comp-class-3 = tigase.test.TestComponent

message-archive/archive-repo-uri=jdbc:mysql://localhost:3306/tigasedb?user=tigase_user&password=tigase_pass&useUnicode=true&characterEncoding=UTF-8&autoCreateUser=true

--sm-plugins=message-archive-xep-0136

sess-man/plugins-conf/message-archive-xep-0136/component-jid=message-archive@liuzh-vh

sess-man/plugins-conf/message-archive-xep-0136/auto=true

Added by Natale Vinto over 4 years ago

Psi clients receive messages because they announce their unavailability by presence, if you disconnect them or just quit Psi there is that action triggered and the server can store messages offline due its internal logic and plugins registered for message stanzas. While in mobile networks instead, if you are not available for a certain amount of time, the server try to send you the message on a broken socket and the message is lost, even if a new xmpp session is started. Then, you should enable XEP-0198 in both clients and server, in order to resume streams and try manage faulty network disconnects

Avatar?id=6023&size=32x32

Added by Artur Hefczyc TigaseTeam over 4 years ago

What library or client do you use on Android? As pointed out by Natale, XEP-0198 is recommended to improve message delivery reliability. The basic XMPP RFC does not give you any way to ensure message is delivered. A couple of extensions address different aspects of the data delivery. XEP-0198 is probably the most basic one which should be considered first. Both the Tigase server and our Android library support this XEP.

Added by shen wr over 4 years ago

thks,I have also encountered this problem, then use XEP-0198 to solve the problem.

I would like to ask another question, can explain the exp-0198 in tigase is how to achieve it??

Added by Wojciech Kapcia TigaseTeam over 4 years ago

Information can be found in Server features -> XEP-0198: Stream Management :

To enable Stream Management you need to add following line to etc/init.properties file to enable Stream Management processor in c2s component: c2s/processors[s]=urn:xmpp:sm:3

Added by shen wr over 4 years ago

hi Wojciech Kapcia :

I really want to know is : where are packets ( for resuming),in memory? in db?

Added by Natale Vinto over 4 years ago

Hi,

they are in memory. You should been able to see a SessionWalker in logs that does the job. They live until resumption timeout expires (default for tigase is 60 seconds)

    (1-8/8)