Feed aggregator

Installation and maintenance: RE: 7.2.0 and init.properties

Tigase XMPP Server Board - 4 hours 9 min ago

Thank you for reporting this issue. It is possible to use both names default_room_config or defaultRoomConfig to adjust default room configuration.
I created issue #5559 with your bug report and already fixed it. Fix will be part of a next snapshot build of Tigase XMPP Server 7.2.0.

Categories: Tigase Forums

Installation and maintenance: RE: MUC Light (XEP-0045+)

Tigase XMPP Server Board - 4 hours 48 min ago

MUC Light is different protocol from MUC, not extension of MUC. Due to that, it requires implementation of MUC Light protocol on the server side.
As I'm aware MUC Light was a temporary solution and a proposal on how MUC could be improved for mobile devices. It was never formally accepted and published as a XEP. Instead MIX specification was created (or is created as it is still work in progress).

To answer your question: Client extension for MUC Light will not work on Tigase as Tigase does not support MUC Light protocol.

Categories: Tigase Forums

Installation and maintenance: RE: MUC Light (XEP-0045+)

Tigase XMPP Server Board - 7 hours 37 min ago

I found solution for another server - may be this info will be helpful for your answer
https://github.com/robbiehanson/XMPPFramework/issues/745

Categories: Tigase Forums

Installation and maintenance: MUC Light (XEP-0045+)

Tigase XMPP Server Board - 7 hours 44 min ago

Hello.
Will be this extension by client side working on Tigase?
https://xmpp.org/extensions/inbox/muc-light.html
Or i need do something from server side?

Categories: Tigase Forums

Installation and maintenance: RE: Where to start after installation?

Tigase XMPP Server Board - Thu, 05/25/2017 - 17:57

Verify that tigase.conf is pointing to the right location for JVM.
Which version of JDK did you install? It should be at least v8

Categories: Tigase Forums

Installation and maintenance: RE: 7.2.0 and init.properties

Tigase XMPP Server Board - Thu, 05/25/2017 - 16:48

I have noticed in MUC documentation that

default_room_config has changed to defaultRoomConfig. Applied this change to init.properties and still getting the

java.lang.RuntimeException: Unsupported conversion to interface java.util.Map

Running Java 1.8

$ java -version java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
Categories: Tigase Forums

Installation and maintenance: RE: Where to start after installation?

Tigase XMPP Server Board - Thu, 05/25/2017 - 10:40

After installation I see two shortcuts: "Manually Start Tigase" and "Install Tigase Windows Service". I tried both, first manually and so the Windows service.

I read the Log files and between many lines these below call my attention, seems that Tigase cannot launch JVM.

STATUS | wrapper | 2017/05/25 08:50:12 | Launching a JVM...
ERROR | wrapper | 2017/05/25 08:50:44 | Startup failed: Timed out waiting for a signal from the JVM.
ERROR | wrapper | 2017/05/25 08:50:44 | JVM did not exit on request, termination requested.
STATUS | wrapper | 2017/05/25 08:50:46 | JVM exited after being requested to terminate.
STATUS | wrapper | 2017/05/25 08:50:51 | Launching a JVM...
INFO | jvm 2 | 2017/05/25 08:51:08 | WrapperManager: Initializing...
INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager:
INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: WARNING - Unable to load the Wrapper's native library 'wrapper.dll'.
INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: The file is located on the path at the following location but
INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: could not be loaded:
INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: C:\Tigase\jars\wrapper.dll
INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: Please verify that the file is both readable and executable by the
INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: current user and that the file has not been corrupted in any way.
INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: One common cause of this problem is running a 32-bit version
INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: of the Wrapper with a 64-bit version of Java, or vica versa.
INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: This is a 64-bit JVM.
INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: Reported cause:
INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: C:\Tigase\jars\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: System signals will not be handled correctly.
INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager:
ERROR | wrapper | 2017/05/25 08:51:23 | Startup failed: Timed out waiting for a signal from the JVM.
ERROR | wrapper | 2017/05/25 08:51:23 | JVM did not exit on request, termination requested.
STATUS | wrapper | 2017/05/25 08:51:23 | JVM exited after being requested to terminate.
STATUS | wrapper | 2017/05/25 08:51:28 | Launching a JVM...
INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: Initializing...
INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager:
INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: WARNING - Unable to load the Wrapper's native library 'wrapper.dll'.
INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: The file is located on the path at the following location but
INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: could not be loaded:
INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: C:\Tigase\jars\wrapper.dll
INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: Please verify that the file is both readable and executable by the
INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: current user and that the file has not been corrupted in any way.
INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: One common cause of this problem is running a 32-bit version
INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: of the Wrapper with a 64-bit version of Java, or vica versa.
INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: This is a 64-bit JVM.
INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: Reported cause:
INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: C:\Tigase\jars\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: System signals will not be handled correctly.
INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager:

Categories: Tigase Forums

Installation and maintenance: RE: Where to start after installation?

Tigase XMPP Server Board - Thu, 05/25/2017 - 09:48

After setup, Tigase XMPP Server is not installed as a service, so it has to be run as an application for first start.
Tigase is not really a native windows exe program, so no start menu or desktop icons were made during installation.
You can either use wrapper.exe or tigase.exe in the installation directory. Output for console log will be in /logs/wrapper.log
Have a look there to see if any warnings or errors pop up to indicate issues running the program.

Categories: Tigase Forums

Installation and maintenance: RE: Where to start after installation?

Tigase XMPP Server Board - Thu, 05/25/2017 - 09:31

Hi, Daniel,

I tried this but seems that there's no webserver running.

Also I tried to login using the Spark XMPP client but without success.

Categories: Tigase Forums

Installation and maintenance: RE: Where to start after installation?

Tigase XMPP Server Board - Thu, 05/25/2017 - 09:14

Hi Jairo,
Our HTTP component provides a web-based configuration method. When your server is running go to
http://localhost:8080/admin/
on your browser and login with the admin JID and password you used during setup. This should provide you access to the administration panel.
http://localhost:8080/ui/ provides access to the web-based client.

Categories: Tigase Forums

Installation and maintenance: Where to start after installation?

Tigase XMPP Server Board - Thu, 05/25/2017 - 09:06

Hello everyone!

I installed Tigase XMPP Server with the options below in a Windows 7 computer (please see the attachments).

But now I'm a little confuse about where to start.
I thought that I would find a web admin panel or something like to manage the server and accounts (like OpenFire) but I've no clue how to do this now.

Someone can give me an light?

Thanks in advance.

Categories: Tigase Forums

Installation and maintenance: 7.2.0 and init.properties

Tigase XMPP Server Board - Wed, 05/24/2017 - 14:01

Hello,

I have noticed the init.properties format has changed quite a bit. Tigase 7.2.0 nightly build has attempted to automatically convert my old file to the new format. It ha some success, but not 100%. Are there any documents available on properly configuring the server yet ?

#config-type = --gen-config-all #--debug = xmpp.XMPPIOService --debug = server.amp,server,xmpp.impl,db,muc,xmpp.XMPPIOService --cluster-mode = false --virt-hosts = domain.com --user-db-uri = UriString --user-db = mysql --admins = admin@domain.com --comp-name-5 = message-archive #--comp-name-4 = rest #--comp-name-3 = proxy #--comp-name-2 = pubsub --comp-name-1 = muc --sm-plugins = -msgoffline,-message,+amp,+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 --comp-class-5 = tigase.archive.MessageArchiveComponent #--comp-class-4 = tigase.http.rest.RestMessageReceiver #--comp-class-3 = tigase.socks5.Socks5ProxyComponent #--comp-class-2 = tigase.pubsub.PubSubComponent --comp-class-1 = tigase.muc.MUCComponent --watchdog_delay=60000 --watchdog_timeout=70000 --watchdog_ping_type=xmpp c2s/processors[s]=urn:xmpp:sm:3 muc/message-filter-enabled[B]=false muc/muc-lock-new-room[B]=false muc/default_room_config/muc#maxhistoryfetch=50 muc/default_room_config/muc#roomconfig_persistentroom=true muc/default_room_config/muc#roomconfig_changesubject=true muc/default_room_config/muc#roomconfig_publicroom=true muc/default_room_config/muc#roomconfig_moderatedroom=false muc/default_room_config/muc#roomconfig_membersonly=false imuc/default_room_config/muc#roomconfig_moderatedroom=false sess-man/plugins-conf/message-archive-xep-0136/default-store-method=message sess-man/plugins-conf/message-archive-xep-0136/required-store-method=message message-archive/archive-repo-uri=UriString #--debug = server.amp,muc basic-conf/logging/tigase.server.level=FINEST basic-conf/logging/tigase.xmpp.impl.level=FINEST basic-conf/logging/tigase.xmpp.XMPPIOService.level=FINEST basic-conf/logging/tigase.db.level=INFO basic-conf/logging/tigase.muc.level=FINEST basic-conf/logging/tigase.server.amp.level=FINEST sess-man/plugins-conf/amp/store-limit[L]=100 sess-man/plugins-conf/amp/quota-exceeded=drop amp/store-limit[L]=100 --amp-security-level=PERFORMANCE --amp-security-level = PERFORMANCE --cluster-mode = false --debug = 'server.amp,server,xmpp.impl,db,muc,xmpp.XMPPIOService' --test = false --virt-hosts = domain.com --watchdog_delay = 60000 --watchdog_ping_type = xmpp --watchdog_timeout = 70000 admins = [ 'admin@domain.com' ] 'config-type' = '--gen-config-default' dataSource { default () { uri = 'uri string' } } userRepository { default () {} } authRepository { default () {} } amp { 'store-limit' = 100L } 'basic-conf' { logging { tigase.db.level = 'INFO' tigase.muc.level = 'FINEST' tigase.server.amp.level = 'FINEST' tigase.server.level = 'FINEST' tigase.xmpp.XMPPIOService.level = 'FINEST' tigase.xmpp.impl.level = 'FINEST' } } c2s { beans = [ 'urn:xmpp:sm:3' ] } #imuc { # default_room_config { # 'muc#roomconfig_moderatedroom' = 'false' # } #} 'message-archive' (class: tigase.archive.MessageArchiveComponent) { archive-repo-uri = 'uri string' } 'muc' (class: tigase.muc.MUCComponent) { # 'message-filter-enabled' = false # 'muc-lock-new-room' = false # 'default_room_config' { # 'muc#maxhistoryfetch' = '50' # 'muc#roomconfig_changesubject' = 'true' # 'muc#roomconfig_membersonly' = 'false' # 'muc#roomconfig_moderatedroom' = 'false' # 'muc#roomconfig_persistentroom' = 'true' # 'muc#roomconfig_publicroom' = 'true' # } } sess-man { beans = [ '-msgoffline,-message,+amp,+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 { 'quota-exceeded' = 'drop' 'store-limit' = 100L } message-archive-xep-0136 (class: tigase.archive.MessageArchivePlugin) { 'default-store-method' = 'message' 'required-store-method' = 'message' } } Loading component: vhost-man :: componentInfo{Title=Tigase XMPP Server, Version=7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01), Class=tigase.vhosts.VHostManager} Loading component: amp :: componentInfo{Title=Tigase XMPP Server, Version=7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01), Class=tigase.server.amp.AmpComponent} Loading component: bosh :: componentInfo{Title=Tigase XMPP Server, Version=7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01), Class=tigase.server.bosh.BoshConnectionManager} Loading component: stats :: componentInfo{Title=Tigase XMPP Server, Version=7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01), Class=tigase.stats.StatisticsCollector} 2017-05-24 20:15:33.979 [main] AbstractBeanConfigurator.registerBeans() WARNING: unknown class null for bean msgoffline,-message,+amp,+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, skipping registration of a bean Loading plugin: amp=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: disco=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: presence-subscription=8:58 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: message-carbons=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: session-close=8:58 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: urn:ietf:params:xml:ns:xmpp-sasl=8:58 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: urn:ietf:params:xml:ns:xmpp-bind=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: urn:xmpp:csi:0=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: urn:xmpp:ping=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: zlib=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: http://jabber.org/protocol/commands=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: starttls=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: jabber:iq:auth=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: jabber:iq:version=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: urn:ietf:params:xml:ns:xmpp-session=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: jabber:iq:register=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: presence-state=8:58 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: vcard-temp=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: urn:xmpp:time=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: urn:xmpp:blocking=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: jabber:iq:privacy=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: message-archive-xep-0136=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) 2017-05-24 20:15:34.134 [main] DNSResolver.<clinit>() WARNING: Resolving default host name: ip-10-0-0-196.eu-west-1.compute.internal took: 1 MA LOADED = message-archive@ip-10-0-0-196.eu-west-1.compute.internal Loading plugin: vcard-xep-0292=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: http://jabber.org/protocol/stats=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: jabber:iq:private=2:233 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: session-open=4:116 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: default-handler=8:58 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading plugin: jabber:iq:roster=8:58 ... , version: 7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01) Loading component: sess-man :: componentInfo{Title=Tigase XMPP Server, Version=7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01), Class=tigase.server.xmppsession.SessionManager} Loading component: c2s :: componentInfo{Title=Tigase XMPP Server, Version=7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01), Class=tigase.server.xmppclient.ClientConnectionManager} Loading component: monitor :: componentInfo{Title=Tigase XMPP Server, Version=7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01), Class=tigase.monitor.MonitorComponent} Loading component: ws2s :: componentInfo{Title=Tigase XMPP Server, Version=7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01), Class=tigase.server.websocket.WebSocketClientConnectionManager} Loading component: s2s :: componentInfo{Title=Tigase XMPP Server, Version=7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01), Class=tigase.server.xmppserver.S2SConnectionManager} Loading component: eventbus :: componentInfo{Title=Tigase XMPP Server, Version=7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01), Class=tigase.eventbus.component.EventBusComponent} Loading component: http :: componentInfo{Title=Tigase HTTP API component: Tigase HTTP API component, Version=1.3.0-SNAPSHOT-b190/509596ee-7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01), Class=tigase.http.HttpMessageReceiver} 2017-05-24 20:15:40.445 [main] DSLBeanConfiguratorWithBackwardCompatibility.configure() WARNING: Class tigase.muc.MUCComponent is using deprecated configuration using methods getDefaults() and setProperties() 2017-05-24 20:15:40.446 [main] Kernel.injectDependencies() WARNING: Could not initialize bean muc (class: class tigase.muc.MUCComponent), skipping injection of this bean 2017-05-24 20:15:40.448 [main] DSLBeanConfiguratorWithBackwardCompatibility.configure() WARNING: Class tigase.archive.MessageArchiveComponent is using deprecated configuration using methods getDefaults() and setProperties() Loading component: message-archive :: componentInfo{Title=Tigase Message Archiving Component, Version=1.2.0-SNAPSHOT-b92/197b1a68-7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01), Class=tigase.archive.MessageArchiveComponent} Loading component: message-router :: componentInfo{Title=Tigase XMPP Server, Version=7.2.0-SNAPSHOT-b4821/bb513114 (2017-05-14/23:10:01), Class=tigase.server.MessageRouter} 2017-05-24 20:15:41.584 [main] DSLBeanConfiguratorWithBackwardCompatibility.configure() WARNING: Class tigase.muc.MUCComponent is using deprecated configuration using methods getDefaults() and setProperties() 2017-05-24 20:15:41.584 [main] Kernel.injectDependencies() WARNING: Could not initialize bean muc (class: class tigase.muc.MUCComponent), skipping injection of this bean 2017-05-24 20:15:41.587 [main] DSLBeanConfigurator.dumpConfiguration() WARNING: Dumping full server configuration to: etc/config-dump.properties == 2017-05-24 20:15:41.689 Server finished starting up and (if there wasn't any error) is ready to use 2017-05-24 20:16:08.094 [ConnectionOpenThread] SocketThread.<clinit>() WARNING: 9 socketReadThreads started. 2017-05-24 20:16:08.098 [ConnectionOpenThread] SocketThread.<clinit>() WARNING: 9 socketWriteThreads started.

There are definitely some issues with message archiving and MUC components. Help please!

Categories: Tigase Forums

API and development: Cannot send MUC chatroom invitations to offline users

Tigase XMPP Server Board - Tue, 05/23/2017 - 06:04

Hi, I need some help here.

We are building an app with latest jaxmpp (2.1) client lib, and running latest Tigase (7.1) as xmpp server. Recently we running into a issue which is we cannot send MUC chatroom invitations to offline users. Direct Invitation and Mediated Invitation both failed. We are sure sending invitation to user's Bare JID.

We tested this case with another xmpp client - PSI, and reproduced this issue.

We also checked xep-0045 (Multi-User Chat) and xep-0249 (Direct MUC Invitations), none of them mentioned offline invitation.

Someone in internet said: Invites to Bare Jids should be stored as offline messages and then delivered by the server as soon as the user comes online. But he does not give any suggestions of how to fix it.

Any message can be help, thanks in advance.

Sorry for my bad English.

Categories: Tigase Forums

Installation and maintenance: RE: What is the max length of a message?

Tigase XMPP Server Board - Wed, 05/10/2017 - 08:57

Igor, we are currently working on smarter SPAM filters so I'm not sure that this particular feature will be needed.

Categories: Tigase Forums

Installation and maintenance: RE: What is the max length of a message?

Tigase XMPP Server Board - Wed, 05/10/2017 - 08:10

It would be greate if it will be possible to limit message.body CDATA because it's kind of the most popular case how people can spam server.
if the limit is exceeded then a reject message can be sent back

Categories: Tigase Forums

API and development: RE: How to suppress error stanza from a pre-processor?

Tigase XMPP Server Board - Thu, 04/27/2017 - 18:35

What exact version/built of the Tigase XMPP Server do you use? This part of the code could have changed over time, so to give you accurate answer I need to know what version of the Tigase you use.

v7.1.0-b4379 is where we're seeing this behaviour.

Oh we'd love to try it out! We are in a process of upgrading from v5.2.2 to v7.1.0, which is where we plan to implement the spam block component. Our dev/lab environment already runs v7.1.0 and we'd love to try what you have so far.

Categories: Tigase Forums

API and development: RE: How to suppress error stanza from a pre-processor?

Tigase XMPP Server Board - Thu, 04/27/2017 - 18:15

What exact version/built of the Tigase XMPP Server do you use? This part of the code could have changed over time, so to give you accurate answer I need to know what version of the Tigase you use.

By the way, we have already started working on anti-abuse code for the Tigase XMPP Server. We already have some spam filtering implemented and deployed to our servers: tigase.org and tigase.im. It works pretty well. I used to get about 100 spam messages per day on tigase.im and now I am not getting even 1 spam message.

Would you be interested in trying it on your system? We have version of the code compatible with Tigase server version 7.1.x and 7.2.x

Categories: Tigase Forums

API and development: How to suppress error stanza from a pre-processor?

Tigase XMPP Server Board - Thu, 04/27/2017 - 18:03

Hi,

We are trying to develop a spam block functionality. Here's a previous discussion from these forums on the recommended approach - https://projects.tigase.org/boards/4/topics/7122?r=7131#message-7131

I think it would be best to go with totally different approach and create preprocessor which forwards <message/> to different component which would be handling message filtering based on remote calls to HTTP server and then sending packets back to SM.

The recommendation is to develop a pre-processor that forwards message stanzas to a custom component, which checks for spam and sends valid messages back to the session manager.

We are able to forward the packets from a XMPPPreprocessorIfc to the custom spam component, but an error stanza is sent to the client when the preProcess() returns 'true'. We want the spam check component to determine if the current packet can be sent to the client. Until that happens, is there a way to suppress this error stanza from session manager to the client?

Any help is appreciated.

Code:
public boolean preProcess(Packet packet, XMPPResourceConnection session, NonAuthUserRepository repo, Queue<Packet> results, Map<String, Object> settings) { boolean isStanzaTypeChat = (packet.getType() == StanzaType.chat); if(!isStanzaTypeChat) { return false; } log.debug("Packet received by pre-processor: {}", packet.toString()); try { JID messageProcessorComponentJid = JID.jidInstance("np-message-processor@gagan.mac"); Packet packetToForward = packet.swapFromTo(); packetToForward.setPacketTo(messageProcessorComponentJid); log.debug("sending following packet to message-processor:\n{}", packetToForward.toStringFull()); results.offer(packetToForward); return true; } catch (TigaseStringprepException e) { log.error("error sending packet to message processor", e); } return false; }

Categories: Tigase Forums

Installation and maintenance: RE: "Impossible happened..." log in tigase.log

Tigase XMPP Server Board - Wed, 04/26/2017 - 16:30
I think the most important is actually more details about the installation, as it might be difficult or impossible to know what caused this issue. Trung, could you please provide us with the following information:
  1. Exact version of the Tigase XMPP Server you are running (ideally build number)
  2. Is it a clustered or non-clustered installation
  3. It would be also very helpful to see Tigase configuration from this system, I understand you may not be able to show us everything but if there is anything you can show us, it would be a big help

By the way, you do not have to worry about this. It does not impact your system, or any of your messaging features.

This happened because you probably configured Tigase to send XMPP pings from the server to clients connected to discover lost connections. Apparently the client side software does not understand the XMPP ping request and responds with an error. Somehow, the Tigase server cannot handle the error correctly and prints this log records. Most likely, the user has disconnected in the meantime, before the server started to process the error stanza.

This can happen in 2 situations:
  1. You have a significant load and such error stanzas are lower priority packets so they wait in a queue, while other packets are being processed, for example information about client disconnected can take over other lower priority packets
  2. Maybe, the client after receiving XMPP ping which it does not understand, sends an error back to the server and then disconnected immediately after that. This is very likely scenario if your system is under low traffic when the log record was written

So, you should actually check if your client side software understands the XMPP ping, if not and it disconnects after receiving the ping, it may cause connectivity problems for your users and you should disable the XMPP ping on your server installation until it is supported by your clients.

Categories: Tigase Forums

Installation and maintenance: RE: "Impossible happened..." log in tigase.log

Tigase XMPP Server Board - Wed, 04/26/2017 - 14:30

Can you share more details what happend that triggered this? Can you extract a distinct use-case?

Categories: Tigase Forums

Pages

Get in touch

We provide software products, consulting and custom development services

Tigase, Inc.
100 Pine Street, Suite 1250
San Francisco, CA 94111, USA
Phone: (415) 315 9771

Follow us on:

Twitter

Back to Top