Tigase XMPP Server Board

API and development: MissingPropertyException

Wed, 06/01/2016 - 03:22

Hi,

I am getting the following exception while running the latest tigase server

java_util_logging_Logger$log.call() SEVERE: Exception loading handler from script = /home/ec2-user/tigase-server-7.0.4-b3844/scripts/rest/stream/Stream.groovy
groovy.lang.MissingPropertyException: No such property: description for class: rest.stream.Stream
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.setGroovyObjectProperty(ScriptBytecodeAdapter.java:530)
at rest.stream.Stream.<init>(Stream.groovy:43)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77)
at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:71)
at groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:1536)
at groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:1404)
at org.codehaus.groovy.runtime.InvokerHelper.invokeConstructorOf(InvokerHelper.java:879)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.newInstance(DefaultGroovyMethods.java:11892)
at org.codehaus.groovy.runtime.dgm$369.invoke(Unknown Source)
at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite$StaticMetaMethodSiteNoUnwrapNoCoerce.invoke(StaticMetaMethodSite.java:148)
at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.call(StaticMetaMethodSite.java:88)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.call(StaticMetaMethodSite.java:93)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112)
at tigase.http.rest.HandlersLoader.loadHandler(HandlersLoader.groovy:41)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:361)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:909)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:66)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:145)
at tigase.http.rest.HandlersLoader$_loadHandlers_closure1.doCall(HandlersLoader.groovy:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:909)
at groovy.lang.Closure.call(Closure.java:411)
at groovy.lang.Closure.call(Closure.java:427)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1326)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1298)
at org.codehaus.groovy.runtime.dgm$148.invoke(Unknown Source)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at tigase.http.rest.HandlersLoader.loadHandlers(HandlersLoader.groovy:51)
at tigase.http.rest.HandlersLoader$loadHandlers.call(Unknown Source)
at tigase.http.rest.RestServlet.loadHandlers(RestServlet.groovy:65)
at tigase.http.rest.RestExtServlet.super$4$loadHandlers(RestExtServlet.groovy)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1085)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodOnSuperN(ScriptBytecodeAdapter.java:128)
at tigase.http.rest.RestExtServlet.loadHandlers(RestExtServlet.groovy:43)
at tigase.http.rest.RestExtServlet$loadHandlers.callCurrent(Unknown Source)
at tigase.http.rest.RestServlet.init(RestServlet.groovy:60)
at javax.servlet.GenericServlet.init(GenericServlet.java:244)
at tigase.http.java.RequestHandler.registerServlet(RequestHandler.java:94)
at tigase.http.java.RequestHandler.<init>(RequestHandler.java:59)
at tigase.http.java.JavaStandaloneHttpServer.deploy(JavaStandaloneHttpServer.java:98)
at tigase.http.java.JavaStandaloneHttpServer.deploy(JavaStandaloneHttpServer.java:77)
at tigase.http.HttpServer.deploy(HttpServer.java:99)
at tigase.http.rest.RestModule.start(RestModule.java:112)
at tigase.http.HttpMessageReceiver.setProperties(HttpMessageReceiver.java:237)
at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:540)
at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:177)
at tigase.conf.Configurator.componentAdded(Configurator.java:50)
at tigase.conf.Configurator.componentAdded(Configurator.java:33)
at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116)
at tigase.server.MessageRouter.addComponent(MessageRouter.java:108)
at tigase.server.MessageRouter.addRouter(MessageRouter.java:145)
at tigase.server.MessageRouter.setProperties(MessageRouter.java:704)
at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:540)
at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:177)
at tigase.conf.Configurator.componentAdded(Configurator.java:50)
at tigase.conf.Configurator.componentAdded(Configurator.java:33)
at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116)
at tigase.server.MessageRouter.addRegistrator(MessageRouter.java:131)
at tigase.server.MessageRouter.setConfig(MessageRouter.java:603)
at tigase.server.XMPPServer.start(XMPPServer.java:142)
at tigase.server.XMPPServer.main(XMPPServer.java:112)

Tigase version : tigase-server-7.0.4-b3844

Please help.
Thank you

Categories: Tigase Forums

API and development: RE: Create an admin user

Tue, 05/31/2016 - 22:12

Thanks for the reply.

If I add admin entries to the init.properties does it require to restart the server. if so is there any way to do it without a restarting the server?

Categories: Tigase Forums

API and development: RE: Create an admin user

Tue, 05/31/2016 - 09:41

Hello Mohammed,
There are two ways you can create users.
1. login with your admin credentials to the admin screen. Admin screen should be http://localhost:8080/admin/ if you are on local machine. Then you can click on Add user and fill in the fields. You will then need to add that jid to the admins line in init.properties.

2. Login with admin credentials using a client like Psi. Use Service Discovery to navigate to Session Manager, and use Add user fields to create user. Again, you will need to add the newly created JID to admins list.

You can have multiple admins in init.properties

--admins=,

Categories: Tigase Forums

Installation and maintenance: RE: jingle protocol support

Tue, 05/31/2016 - 00:06

Updates?

Categories: Tigase Forums

API and development: Create an admin user

Mon, 05/30/2016 - 22:27

Hi,

How can i create new administrators once the tigase is installed and running.

Categories: Tigase Forums

API and development: RE: Tigase Eclipse Code Formatter

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

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: jingle protocol support

Thu, 05/19/2016 - 22:03

Any updates?

Categories: Tigase Forums

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

Thu, 05/19/2016 - 10:59

Working perfectly now. Thanks :)

Categories: Tigase Forums

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

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

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: RE: Dynamic relesase component

Thu, 05/19/2016 - 02:05

thinks!

Categories: Tigase Forums

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

Thu, 05/19/2016 - 00:48

Issue has been fixed, thank you!

Categories: Tigase Forums

API and development: Tigase Eclipse Code Formatter

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

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

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

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

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

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

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

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

  • New blog post going into some MUC basics https://t.co/o1HoDzrAHM 9 hours 18 min ago
  • A new version of Tigase JaXMPP Client LIbrary has been released, now v3.1.2. Check out the release notes: https://t.co/JiMF85BG8G 2 weeks 20 hours ago
Back to Top