Feed aggregator

API and development: RE: Tigase Eclipse Code Formatter

Tigase XMPP Server Board - Wed, 05/25/2016 - 03:02

Currently we don't provide such file (and no-one in our team uses Eclipse…).

Categories: Tigase Forums

Installation and maintenance: Pending SM messages lost during shutdown

Tigase XMPP Server Board - Fri, 05/20/2016 - 02:07

Hello project members,
I noticed that if messages are in Session Management (as in XEP-0198) queue, if the server shuts down and messages are still pending because of a network issue on the recipient side, those messages are lost forever. I had a couple of controlled cases, is that possible that those messages are not handled at all by design?

I'm using the offlinemsg plugin and not using AMP for storing messages. I know the offlinemsg plugin quite well and I know it deletes messages from the database before they are even delivered, so might it cause message loss on server shutdown?

Also, SM resumption is not enabled by my clients, but I don't know it makes a difference in this case (does it?)

Thanks

Categories: Tigase Forums

Installation and maintenance: RE: [website] projects.tigase.org certificate expired

Tigase XMPP Server Board - Thu, 05/19/2016 - 10:55

An errant redirect as I was finishing up...

Categories: Tigase Forums

Installation and maintenance: RE: [website] projects.tigase.org certificate expired

Tigase XMPP Server Board - Thu, 05/19/2016 - 10:20

Wait, now it doesn't work again. Here is the output from:

openssl s_client -connect repository.tigase.org:443 CONNECTED(00000003) 140684613084824:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:794: --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 7 bytes and written 305 bytes --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 Cipher : 0000 Session-ID: Session-ID-ctx: Master-Key: Key-Arg : None PSK identity: None PSK identity hint: None SRP username: None Start Time: 1463678356 Timeout : 300 (sec) Verify return code: 0 (ok) ---

This morning was working.

Categories: Tigase Forums

API and development: Tigase Eclipse Code Formatter

Tigase XMPP Server Board - Wed, 05/18/2016 - 17:00

Hi All,

Is there a coding style somewhere or configuration to allow for auto formatting in eclipse. This is formatting to follow tigase's coding standards, also is this coding standard noted somewhere?

Cheers :)

Categories: Tigase Forums

Installation and maintenance: RE: [website] projects.tigase.org certificate expired

Tigase XMPP Server Board - Wed, 05/18/2016 - 13:52

All those issues have been fixed. Daniele Ricci can you confirm git is working on your Debian system?

Categories: Tigase Forums

Installation and maintenance: RE: jingle protocol support

Tigase XMPP Server Board - Wed, 05/18/2016 - 10:28

Centos 7 x64

`--# java -version
java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)

`--# hostname
chat.mydomain.com

`--# cat /etc/hosts
127.0.0.1 localhost chat chat.mydomain.com
185.135.111.22 chat.mydomain.com

`--# ifconfig
enp2s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 185.135.111.22 netmask 255.255.255.228 broadcast 185.135.111.100
inet6 2xxx:xx0:xx:0:185.135.111.22 prefixlen 48 scopeid 0x0<global>
inet6 fe80::xxx:xxx:xxxx:xxxx prefixlen 64 scopeid 0x20<link>
ether 00:xx:xx:x0:xx:x6 txqueuelen 1000 (Ethernet)
RX packets 91743516 bytes 14194323403 (3.2 GiB)
RX errors 0 dropped 3822370 overruns 0 frame 0
TX packets 116344994 bytes 86909430445 (0.9 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xfdsf80000-feb9ffff

Categories: Tigase Forums

Installation and maintenance: RE: jingle protocol support

Tigase XMPP Server Board - Wed, 05/18/2016 - 09:34

Here are my results from test which I just executed on my local machine (OSX):
udp4 0 0 172.16.0.2.3578 *.* udp4 0 0 172.16.0.2.7000 *.* udp4 0 0 127.0.0.1.3578 *.* udp4 0 0 127.0.0.1.7000 *.*

As you can see proper UDP ports are opened using udp4. I got this results with following configuration:
--comp-name-3=stun --comp-class-3=tigase.stun.StunComponent stun/stun-primary-ip=127.0.0.1 stun/stun-primary-port[I]=7000 stun/stun-secondary-ip=172.16.0.2 stun/stun-secondary-port[I]=3578 stun/stun-primary-external-port[I]=8000 stun/stun-secondary-external-port[I]=9000

Due to that I suppose that this issue must be caused by system configuration, JVM version or wrong IP configuration.
Could you post your OS name and version, JVM name and version and configuration of IP addresses (result of ipconfig or ifconfig)?

Categories: Tigase Forums

Installation and maintenance: RE: jingle protocol support

Tigase XMPP Server Board - Wed, 05/18/2016 - 09:01

I don't know how are you testing...

But if i try use short configuration (without external)
i see the same messages in tigase logs

> logs/tigase.log <
2016-05-18 15:57:52,362 [Thread-4103] DEBUG d.javawi.jstun.header.MessageHeader - Binding Request received.

And next results with netstat
`--# netstat -an|grep 3478
udp6 0 0 127.0.0.1:3478 :::*
udp6 0 0 185.135.111.22:3478 :::*

As you can see, stun is worked, but with udp6 protocol. So, it's problem.

Categories: Tigase Forums

Installation and maintenance: RE: jingle protocol support

Tigase XMPP Server Board - Wed, 05/18/2016 - 07:43

Hi,

I think that you should use following config, however STUN protocol suggest using 2 IP addresses and may fail to work with single IP address.
--comp-name-4 = stun --comp-class-4 = tigase.stun.StunComponent stun/stun-primary-ip=185.135.111.22 stun/stun-primary-port[I]=3478 stun/stun-secondary-ip=185.135.111.22 stun/stun-secondary-port[I]=7001

As i see, Tigase stun working only with IPv6.

I do not see point in using STUN in IPv6 networks as STUN server is used to deal with NAT and in IPv6 networks there is no NAT.
We tested STUN in IPv4 networks and it worked fine, however if I remember correctly we used setup with 2 IP addresses, not single IP address as with single IP address it STUN protocol was not able to properly deal with some types of NAT

Categories: Tigase Forums

API and development: RE: Dynamic relesase component

Tigase XMPP Server Board - Wed, 05/18/2016 - 07:29

Tigase XMPP Server is able to enable, disable and reconfigure components on request, however to be able to change component (ie. by newer version) it is required to use Tigase XMPP Server in OSGi container. This OSGi container will allow you to replace versions of components at runtime.

Categories: Tigase Forums

Installation and maintenance: RE: jingle protocol support

Tigase XMPP Server Board - Tue, 05/17/2016 - 23:49

And one more question:
As i see, Tigase stun working only with IPv6.
How i can started it for IPv4 ? (i think issue in this place)

Categories: Tigase Forums

API and development: Dynamic relesase component

Tigase XMPP Server Board - Tue, 05/17/2016 - 20:37

hi!
I replace component jar file with slight changed after removed this comp via web console. then add it, but changes doesn't affect.
Does it support reload the component jar?
thx!

Categories: Tigase Forums

Installation and maintenance: RE: jingle protocol support

Tigase XMPP Server Board - Tue, 05/17/2016 - 13:45

After some setting and changes

i see this messages in logs

=> logs/tigase.log <==
2016-05-17 20:42:42,802 [Thread-4097] DEBUG d.javawi.jstun.header.MessageHeader - Binding Request received.
2016-05-17 20:42:44,661 [Thread-4097] DEBUG d.javawi.jstun.header.MessageHeader - Binding Request received.
2016-05-17 20:42:46,662 [Thread-4097] DEBUG d.javawi.jstun.header.MessageHeader - Binding Request received.
2016-05-17 20:42:48,665 [Thread-4097] DEBUG d.javawi.jstun.header.MessageHeader - Binding Request received.

But stun client still can't connected (get info from stun)

and results all time is

--> pystun -d -H chat.DOMAIN.com -P 3478
DEBUG:pystun:Do Test1
DEBUG:pystun:sendto: ('chat.DOMAIN.com', 3478)
DEBUG:pystun:sendto: ('chat.DOMAIN.com', 3478)
DEBUG:pystun:sendto: ('chat.DOMAIN.com', 3478)
DEBUG:pystun:sendto: ('chat.DOMAIN.com', 3478)
NAT Type: Blocked
External IP: None
External Port: None

Categories: Tigase Forums

Installation and maintenance: RE: jingle protocol support

Tigase XMPP Server Board - Tue, 05/17/2016 - 05:29

Could you explain me how i can add stun server component save/show log in Tigase?

At the moment i have got two problems.

When i try connect to 3478 port

@==> logs/tigase-console.log <==
2016-05-17 13:57:19.646 [Thread-4102] ThreadExceptionHandler.uncaughtException() SEVERE: Uncaught thread: "Thread-4102" exception
java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
at de.javawi.jstun.header.MessageHeader.<clinit>(MessageHeader.java:41)
at tigase.stun.StunServerReceiverThread.run(StunServerReceiverThread.java:69)
Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at de.javawi.jstun.header.MessageHeader.<clinit>(MessageHeader.java:41)
at tigase.stun.StunServerReceiverThread.run(StunServerReceiverThread.java:69)

> logs/tigase.log.0 <
2016-05-17 13:57:19.646 [Thread-4102] ThreadExceptionHandler.uncaughtException() SEVERE: Uncaught thread: "Thread-4102" exception
java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
at de.javawi.jstun.header.MessageHeader.<clinit>(MessageHeader.java:41)
at tigase.stun.StunServerReceiverThread.run(StunServerReceiverThread.java:69)
Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at de.javawi.jstun.header.MessageHeader.<clinit>(MessageHeader.java:41)
at tigase.stun.StunServerReceiverThread.run(StunServerReceiverThread.java:69)@

And this when connect to 7001

@==> logs/tigase-console.log <==
2016-05-17 13:57:45.535 [Thread-4103] ThreadExceptionHandler.uncaughtException() SEVERE: Uncaught thread: "Thread-4103" exception
java.lang.NoClassDefFoundError: Could not initialize class de.javawi.jstun.header.MessageHeader
at tigase.stun.StunServerReceiverThread.run(StunServerReceiverThread.java:69)

> logs/tigase.log.0 <
2016-05-17 13:57:45.535 [Thread-4103] ThreadExceptionHandler.uncaughtException() SEVERE: Uncaught thread: "Thread-4103" exception
java.lang.NoClassDefFoundError: Could not initialize class de.javawi.jstun.header.MessageHeader
at tigase.stun.StunServerReceiverThread.run(StunServerReceiverThread.java:69)@

So, what i am do wrong?

Categories: Tigase Forums

API and development: RE: Jingle support for audio / video sharing in XMPP session?

Tigase XMPP Server Board - Tue, 05/17/2016 - 04:48

There is https://projects.tigase.org/issues/440 issue, and probably audio/video support will be added to the library while this feature will be implemented.

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