Project

General

Profile

how can i set init.properties to store all messages for both private and group chat?

peirong jiang
Added over 3 years ago

how can i set init.properties to store all messages for both private and group chat?

my init.properties:

# message-archive-xep-0136  [message|body]
--sm-plugins=message-archive-xep-0136
message-archive/auto=true
sess-man/plugins-conf/message-archive-xep-0136/component-jid=message-archive@10.5.1.12
sess-man/plugins-conf/message-archive-xep-0136/default-store-method=message
sess-man/plugins-conf/message-archive-xep-0136/required-store-method=message
sess-man/plugins-conf/message-archive-xep-0136/store-muc-messages=user
muc/history-db=pgsql
muc/history-db-uri=jdbc:postgresql://10.5.1.12/tigasedb?user=postgres&password=123456&useUnicode=true&characterEncoding=UTF-8&autoCreateUser=true
muc/muc-lock-new-room[B]=false
muc/muc-allow-chat-states[B]=true
conference/message-filter-enabled[B]=false
#persistent room
muc/default_room_config/muc#roomconfig_persistentroom=true

now I can't find the all messages of both the one-to-one and group chat in database.

only the offline messages could be found.

I appreciate if I can get your help!

i appreciate if i can get your help!

init.properties (3.17 KB) init.properties my conf
mydb.png (21 KB) mydb.png

Replies (7)

Added by Wojciech Kapcia TigaseTeam over 3 years ago

Which version of component do you use? Have you tried with setting the value to @true@?

Added by peirong jiang over 3 years ago

what do you mean?

my starting log:

Loading component: amp :: componentInfo{Title=Tigase XMPP Server, Version=7.0.2-b3821/563fcf81 (2015-05-15/00:41:16), Class=tigase.server.amp.AmpComponent}

Loading component: bosh :: componentInfo{Title=Tigase XMPP Server, Version=7.0.2-b3821/563fcf81 (2015-05-15/00:41:16), Class=tigase.server.bosh.BoshConnectionManager}

Loading component: c2s :: componentInfo{Title=Tigase XMPP Server, Version=7.0.2-b3821/563fcf81 (2015-05-15/00:41:16), Class=tigase.server.xmppclient.ClientConnectionManager}

Loading component: http :: componentInfo{Title=Tigase HTTP API component: Tigase HTTP API component, Version=1.1.0-b83/d51e1db6, Class=tigase.http.HttpMessageReceiver}

Loading component: message-archive :: componentInfo{Title=Tigase Message Archiving Component, Version=1.1.0-b71/c4003eb3, Class=tigase.archive.MessageArchiveComponent}

Loading component: monitor :: componentInfo{Title=Tigase XMPP Server, Version=7.0.2-b3821/563fcf81 (2015-05-15/00:41:16), Class=tigase.server.monitor.MonitorComponent}

Loading component: muc :: componentInfo{Title=Tigase MUC, Version=2.3.0-b389/879168a9, Class=tigase.muc.MUCComponent}

Loading component: proxy :: componentInfo{Title=Tigase Socks5 Component, Version=1.1.0-b48/f5c8a08c, Class=tigase.socks5.Socks5ProxyComponent}

Loading component: pubsub :: componentInfo{Title=Tigase PubSub, Version=3.1.0-b463/1df4d937, Class=tigase.pubsub.PubSubComponent}

Loading component: s2s :: componentInfo{Title=Tigase XMPP Server, Version=7.0.2-b3821/563fcf81 (2015-05-15/00:41:16), Class=tigase.server.xmppserver.S2SConnectionManager}

Loading plugin: session-close=4:1265 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: session-open=4:1265 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: default-handler=4:1265 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: jabber:iq:register=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: jabber:iq:auth=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: urn:ietf:params:xml:ns:xmpp-sasl=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: urn:ietf:params:xml:ns:xmpp-bind=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: urn:ietf:params:xml:ns:xmpp-session=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: jabber:iq:roster=2:2530 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: jabber:iq:privacy=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: jabber:iq:version=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: http://jabber.org/protocol/stats=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: starttls=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: vcard-temp=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: http://jabber.org/protocol/commands=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: jabber:iq:private=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: urn:xmpp:ping=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: presence=2:2530 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: disco=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: zlib=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: amp=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: message-carbons=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Loading plugin: message-archive-xep-0136=1:5060 ... , version: 7.0.2-b3821/563fcf81 (2015-05-15/00:41:16)

Added by Wojciech Kapcia TigaseTeam over 3 years ago

peirong jiang wrote:

what do you mean?

my starting log:

Loading component: message-archive :: componentInfo{Title=Tigase Message Archiving Component, Version=1.1.0-b71/c4003eb3, Class=tigase.archive.MessageArchiveComponent}

And on wiki documentation you have information that this will work with the latest development version:

Automatic archiving of MUC messages in user message archive (since 1.2.0-SNAPSHOT)

Added by Selva Valluvan over 3 years ago

I am running tigase 7.0.2 and I added the "sess-man/plugins-conf/message-archive-xep-0136/store-muc-messages=true" into my init.properties file. Restarted the server.

The MUC messages are nor stored in the db still. If I replace tigase-message-archiving.jar with tigase-message-archiving-1.2.0-SNAPSHOT.jar, the server fails to run and giving version error. (see attached)

How should i fix this?

Added by Andrzej Wójcik IoT 1 CloudTigaseTeam over 3 years ago

To store MUC messages in Message Archiving component you need to run version 1.2.0-SNAPSHOT which will run only with Tigase XMPP Server 7.1.0-SNAPSHOT or newer, so you would need to upgrade Tigase XMPP Server to version 7.1.0-SNAPSHOT. Right now we are working on releasing stable version of Tigase XMPP Server 7.1.0.

Added by Selva Valluvan over 3 years ago

Thanks. I have been looking for tigase 7.1.0-SNAPSHOT all over the website couldn't find the link. How can i get Tigase XMPP Server version 7.1.0-SNAPSHOT.

Added by Andrzej Wójcik IoT 1 CloudTigaseTeam over 3 years ago

As there is not official stable release of version 7.1.0, we do not publish it directly on our pages, but our daily builds are available at http://build.tigase.org/nightlies/dists/

    (1-7/7)