Tigase XMPP Server Board

API and development: RE: tigase cluster init.properties

Wed, 06/14/2017 - 08:36

Tigase clustering doesn't required much configuration - please see the guide: http://docs.tigase.org/tigase-server/snapshot/Administration_Guide/html_chunk/tigaseClustering.html

Categories: Tigase Forums

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

Wed, 06/14/2017 - 06:53

Thanks sir. By follow your advice, we just passed the test case for invitations to offline users.

Categories: Tigase Forums

API and development: tigase cluster init.properties

Mon, 06/12/2017 - 08:48

Hello, I would like to deploy the tigase cluster, but have failed, hoping to have a complete tigase cluster reference configuration file.

Categories: Tigase Forums

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

Mon, 06/05/2017 - 12:08

Those invitations don't have <body/> element hence they are not stored by default, but you can adjust Tigase configuration and enable storing them: Storing offline messages without body content

Categories: Tigase Forums

Installation and maintenance: RE: 7.2.0 and init.properties

Tue, 05/30/2017 - 07:55

I'm not sure, which build of Tigase XMPP Server you used to update a configuration file from properties to DSL, but for me newest build properly uses:
--virt-hosts = 'domain1.com,domain2.com'
instead of
--virt-hosts = domain1.com, domain2.com

As for error:
- Unknown class null for bean basic-filter
it is the result of:
,+basic-filter,
within beans property value within sess-man section. I would suggest to remove this entry as I'm not able to find SessionManager processor with basic-filter identifier.

Categories: Tigase Forums

Installation and maintenance: RE: 7.2.0 and init.properties

Sun, 05/28/2017 - 01:38

Hi,

MUC config issue now gone!

Here is another one:

inside init.properties
--virt-hosts = domain1.com, domain2.com

inside tigase-console.log
--virt-hosts = domain1.com

domain2.com accounts not working

Oh, and

- Unknown class null for bean basic-filter

is still there too.

Thanks!

Categories: Tigase Forums

Installation and maintenance: RE: 7.2.0 and init.properties

Fri, 05/26/2017 - 10:29

I'm not sure about the cache, but it should be disabled only in cluster mode.
Issues with bean being null is most likely a result of failure to configure MUC component.
PubSub is loaded as we changed which components are loaded by default. To disable it you will need to disable it in a config file.

Categories: Tigase Forums

Installation and maintenance: RE: 7.2.0 and init.properties

Fri, 05/26/2017 - 10:18

Great, I'll give it a go later. Any words about those other issues from my first post ?

Categories: Tigase Forums

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

Fri, 05/26/2017 - 05:56

Yes, I already (1) verify the path to JDK folder in tigase.conf

"C:\Program Files (x86)\Java\jdk1.8.0_131\bin\java" -cp "jars/*" -Djdbc.drivers=com.mysql.jdbc.Driver tigase.server.XMPPServer --property-file etc/init.properties

and (2) I put the complete path to java.exe in Run.bat and (3) reinstall Tigase but none works.

JAVA_HOME="C:\Program Files (x86)\Java\jdk1.8.0_131"
CLASSPATH=""
#PRODUCTION_HEAP_SETTINGS=" -Xms5G -Xmx5G " # heap memory settings must be adjusted on per deployment-base!
JAVA_OPTIONS="${GC} ${GC_DEBUG} ${EX} ${ENC} ${DRV} ${JMX_REMOTE_IP} -server ${PRODUCTION_HEAP_SETTINGS} ${DNS_RESOLVER} ${INTERNAL_IP} ${EXTERNAL_IP} -XX:MaxDirectMemorySize=128m "
TIGASE_OPTIONS=" --property-file etc/init.properties "

Thank you, Daniel!
But nothing seems to work in Windows, now I'll try in a Raspberry with Debian.

Have a good day!

Categories: Tigase Forums

Installation and maintenance: RE: 7.2.0 and init.properties

Fri, 05/26/2017 - 03:48

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+)

Fri, 05/26/2017 - 03:10

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+)

Fri, 05/26/2017 - 00:21

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+)

Fri, 05/26/2017 - 00:14

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?

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

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?

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?

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?

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?

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

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

  • Tigase Messenger for iOS has been updated to v1.1 so we made a little video to celebrate! Get it here:… https://t.co/p7rJI8KhMQ 2 days 10 hours ago
  • Tigase Messenger for iOS Beta version has received an update to v1.1. Visit https://t.co/SjCptS1ZYS for patch notes. 1 week 6 days ago
Back to Top