Feed aggregator

Tigase server development: RE: Push Notifications for 1:1 and MUC Offline Users

Tigase XMPP Server Board - Fri, 04/17/2015 - 08:42

Not yet. We are yet to close all bugs and create a public git repo. Possibly within June we should have put it on public repo.

Categories: Tigase Forums

Tigase server development: RE: Message not delivered until stream management timeout time expires

Tigase XMPP Server Board - Fri, 04/17/2015 - 04:14

Hi Andrzej,

I found this row in the logs, but it looks like this is the server sending something to the client, while you suggested to look at something on the opposite way:

2015-04-17 10:55:22.595 [in_2-c2s] ClientConnectionManager.processCommand() FINEST: Sending stream close to the client: <stream:error><conflict xmlns="urn:ietf:params:xml:ns:xmpp-streams"/></stream:error></stream:stream>

Does this mean that the server received the message and that answered back or there is something missing ?

BTW, if I reconnect I find the row:

2015-04-17 10:56:19.896 [pool-14-thread-5] ClientConnectionManager.xmppStreamOpened() FINER: Writing raw data to the socket: <?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' from='vhost.acme.net' id='7a01531d-5610-41e1-b5f4-ff054c8dcfd1' version='1.0' xml:lang='en'>

But this is just the stream opening, nothing related with the logout process.

Does this give you any hint to see if there is something wrong going on ?

Thanks in advance,
Luca

Categories: Tigase Forums

Tigase server development: RE: Push Notifications for 1:1 and MUC Offline Users

Tigase XMPP Server Board - Fri, 04/17/2015 - 03:08

Hi Ganesh,

Are you open sourced your fork ??

Categories: Tigase Forums

Tigase server administration: RE: Does my init.properties look good? What's --c2s-ports ??

Tigase XMPP Server Board - Fri, 04/17/2015 - 00:02
  1. JeSuisTigase wrote:

Hi,

I'm trying to allow connection from a webrowser (strophejs) to my tigase server via bosch, through the port 5281 with SSL.

What do I have to do? I juste have to modify my file init.properties, isn't ?
here it is :

--bosh-ports=5281
bosh/connections/5281/socket=ssl
bosh/connections/5281/type=accept

Yes, this is the needed configuration.

Moreover, what is the purpose of this property ? :

--c2s-ports=5281
c2s/5281/port_type=plain

the c2s is the regular socket so you should not configure it on the same port as you just configured bosh. The port_type defines whether it should be, well, plain or encrypted.

Categories: Tigase Forums

Tigase server administration: RE: I am using xmpp server and i am getting intermediate 502 error ...

Tigase XMPP Server Board - Thu, 04/16/2015 - 23:57

OK, as the log indicates Tigase closes connection for some reason, and without any excerpt from logs (mostly Tigase) it's hard to tell why it behaves like that. Please recreate the issue with debugging enabled in Tigase and cleared logs (--debug=server,xmpp.impl,net,io,bosh) and check those logs for entries with closing the connection.

Categories: Tigase Forums

Tigase server development: RE: Message not delivered until stream management timeout time expires

Tigase XMPP Server Board - Thu, 04/16/2015 - 12:31

I never have a case in which proper device logout caused stream resumption to keep stream open. In every case in 7.0.0 when stream was closed properly then stream resumption did not start resumption timeout as this timeout is only started when client closes connection without sending stream termination, but if XMPP client fails to send:
</stream:stream>
then stream management starts timeout which will lead to this behavior.

From attached log I cannot say if client sent stream termination as this was in log before attached part. This part only shows handling of stream termination due to TCP connection disconnection.

As for keeping messages in memory during stream management timeout - this is correct and expected behavior.

Categories: Tigase Forums

Tigase server development: Message not delivered until stream management timeout time expires

Tigase XMPP Server Board - Thu, 04/16/2015 - 09:02

Hi there,

I am experiencing a curious behavior and I wanted to ask you if this is expected or not, and how to improve the situation.

Let me go straight to the issue: I am testing on Tigase 7.0.0 this scenario, with Stream Management on both on server and client:

  • A mobile device is logged in the server.
  • That device successfully logs out and correctly announces the disconnection
  • After a few seconds I send a message to that user (same resource)
  • The message can't be delivered, but it's not persisted immediately on the DB (I kinda expected it, but it does not happen)
  • After the stream management timeout triggers, the message is either persisted (if the device didn't return online) or sent directly to the device

Is this behavior correct or at least expected ?
Is there a way to activate the stream management that does not imply waiting the timeout before receiving such a message for users that correctly logged out of the server ?

Below there is an extract of the logs in which we see that

2015-04-16 15:20:21.503 [pool-14-thread-1] StreamManagementIOProcessor.serviceStopped() FINEST: c2s@localhost/172.31.18.86_5222_151.44.133.199_63029, type: accept, Socket: TLS: c2s@localhost/172.31.18.86_5222_151.44.133.199_63029 Socket[unconnected], jid: user@vhost.acme.net/XMPPFramework, service stopped - checking resumption timeout 2015-04-16 15:21:21.503 [scheduler_pool-6-thread-1-c2s] ConnectionManager.serviceStopped() FINER: [[c2s]] Connection stopped: c2s@localhost/172.31.18.86_5222_151.44.133.199_63029, type: accept, Socket: TLS: c2s@localhost/172.31.18.86_5222_151.44.133.199_63029 Socket[unconnected], jid: user@vhost.acme.net/XMPPFramework 2015-04-16 15:21:21.503 [scheduler_pool-6-thread-1-c2s] ClientConnectionManager.xmppStreamClosed() FINER: Stream closed: c2s@localhost/172.31.18.86_5222_151.44.133.199_63029 2015-04-16 15:21:21.504 [scheduler_pool-6-thread-1-c2s] ClientConnectionManager.xmppStreamClosed() FINE: Service stopped, sending packet: from=c2s@localhost/172.31.18.86_5222_151.44.133.199_63029, to=sess-man@localhost, DATA=<iq from="c2s@localhost/172.31.18.86_5222_151.44.133.199_63029" to="sess-man@localhost" id="ecd44759-4cf1-4ec8-ad98-ab25f43b006a" type="set"><command xmlns="http://jabber.org/protocol/commands" node="STREAM_CLOSED"><x xmlns="jabber:x:data" type="submit"><field var="user-jid"><value>user@vhost.acme.net/XMPPFramework</value></field></x></command></iq>, SIZE=356, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=set 2015-04-16 15:21:21.504 [scheduler_pool-6-thread-1-c2s] StreamManagementIOProcessor.serviceStopped() FINEST: c2s@localhost/172.31.18.86_5222_151.44.133.199_63029, type: accept, Socket: TLS: c2s@localhost/172.31.18.86_5222_151.44.133.199_63029 Socket[unconnected], jid: user@vhost.acme.net/XMPPFramework, service stopped - checking resumption timeout 2015-04-16 15:21:21.504 [in_2-message-router] MessageRouter.processPacket() FINEST: Processing packet: from=c2s@localhost/172.31.18.86_5222_151.44.133.199_63029, to=sess-man@localhost, DATA=<iq from="c2s@localhost/172.31.18.86_5222_151.44.133.199_63029" to="sess-man@localhost" id="ecd44759-4cf1-4ec8-ad98-ab25f43b006a" type="set"><command xmlns="http://jabber.org/protocol/commands" node="STREAM_CLOSED"><x xmlns="jabber:x:data" type="submit"><field var="user-jid"><value>user@vhost.acme.net/XMPPFramework</value></field></x></command></iq>, SIZE=356, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=set 2015-04-16 15:21:21.504 [in_2-message-router] MessageRouter.getLocalComponent() FINEST: Called for : sess-man@localhost 2015-04-16 15:21:21.504 [in_2-message-router] MessageRouter.getLocalComponent() FINEST: Called for : sess-man@localhost 2015-04-16 15:21:21.504 [in_2-message-router] MessageRouter.processPacket() FINEST: 1. Packet will be processed by: sess-man@localhost, from=c2s@localhost/172.31.18.86_5222_151.44.133.199_63029, to=sess-man@localhost, DATA=<iq from="c2s@localhost/172.31.18.86_5222_151.44.133.199_63029" to="sess-man@localhost" id="ecd44759-4cf1-4ec8-ad98-ab25f43b006a" type="set"><command xmlns="http://jabber.org/protocol/commands" node="STREAM_CLOSED"><x xmlns="jabber:x:data" type="submit"><field var="user-jid"><value>user@vhost.acme.net/XMPPFramework</value></field></x></command></iq>, SIZE=356, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=set 2015-04-16 15:21:21.504 [in_6-sess-man] SessionManager.processPacket() FINEST: Received packet: from=c2s@localhost/172.31.18.86_5222_151.44.133.199_63029, to=sess-man@localhost, DATA=<iq from="c2s@localhost/172.31.18.86_5222_151.44.133.199_63029" to="sess-man@localhost" id="ecd44759-4cf1-4ec8-ad98-ab25f43b006a" type="set"><command xmlns="http://jabber.org/protocol/commands" node="STREAM_CLOSED"><x xmlns="jabber:x:data" type="submit"><field var="user-jid"><value>CData size: 38</value></field></x></command></iq>, SIZE=356, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=set 2015-04-16 15:21:21.504 [in_6-sess-man] SessionManager.processCommand() FINER: STREAM_CLOSED command from: c2s@localhost/172.31.18.86_5222_151.44.133.199_63029 2015-04-16 15:21:21.504 [session-close Queue Worker 3] SessionManager$SessionCloseProc.process() FINEST: Executing connection close for: from=c2s@localhost/172.31.18.86_5222_151.44.133.199_63029, to=sess-man@localhost, DATA=<iq from="c2s@localhost/172.31.18.86_5222_151.44.133.199_63029" to="sess-man@localhost" id="ecd44759-4cf1-4ec8-ad98-ab25f43b006a" type="set"><command xmlns="http://jabber.org/protocol/commands" node="STREAM_CLOSED"><x xmlns="jabber:x:data" type="submit"><field var="user-jid"><value>user@vhost.acme.net/XMPPFramework</value></field></x></command></iq>, SIZE=356, XMLNS=null, PRIORITY=SYSTEM, PERMISSION=NONE, TYPE=set

Thanks in advance,
Luca

Categories: Tigase Forums

Tigase server administration: Does my init.properties look good? What's --c2s-ports ??

Tigase XMPP Server Board - Thu, 04/16/2015 - 05:54

Hi,

I'm trying to allow connection from a webrowser (strophejs) to my tigase server via bosch, through the port 5281 with SSL.

What do I have to do? I juste have to modify my file init.properties, isn't ?
here it is :

config-type=--gen-config-all
--cluster-mode = false
--cluster-nodes = im.wonderchat.com
--admins =
--virt-hosts = im.wonderchat.com
--bosh-ports=5281
bosh/connections/5281/socket=ssl
bosh/connections/5281/type=accept
bosh/max-inactivity[L]=60
bosh/max-wait[L]=30
--user-db = mysql
--user-db-uri = jdbc:mysql://localhost/tigasedb?user=tigase&password=tigase
--comp-name-1 = search
--comp-class-1 = com.wonderchat.tigase.UserRepositoryJabberSearch
--comp-name-2 = conference
--comp-class-2 = tigase.muc.MUCComponent
--debug = server,bosh
--debug-packages = com.wonderchat.tigase
message-router/updates-checking[B]=false
--auth-db = com.wonderchats.tigase.CASAuth
--auth-db-uri = https://wonderchat.com/cas/proxyValidate
basic-conf/auth-repo-params/service-ticket-validation=https://wonderchat.com/cas/proxyValidate
basic-conf/auth-repo-params/alt-auth-db=mysql
basic-conf/auth-repo-params/alt-auth-db-uri=jdbc:mysql://localhost/tigasedb?user=tigase&password=tigase
--debug-packages = com.wonderchat.tigase

Moreover, what is the purpose of this property ? :

--c2s-ports=5281
c2s/5281/port_type=plain

Categories: Tigase Forums

Tigase server administration: RE: I am using xmpp server and i am getting intermediate 502 error ...

Tigase XMPP Server Board - Wed, 04/15/2015 - 22:29

Hello Wojciech,

Thanks for replying. I made changes as suggested by you but unfortunately still facing same problem. please suggest.

Categories: Tigase Forums

Tigase server development: RE: Tigase server takes too much time for processing messages.

Tigase XMPP Server Board - Wed, 04/15/2015 - 04:26

As the logs/exception suggests - you seem to try to send messages over connection that hasn't been yet authorized.
tigase.xmpp.NotAuthorizedException: Session has not been yet authorised.

Categories: Tigase Forums

Tigase server administration: RE: Is it possible to change the log level at runtime?

Tigase XMPP Server Board - Wed, 04/15/2015 - 04:23

You can enable JMX (i.e. monitoring in Tigase) connectivity and manage log level that way at runtime (for example through jConsole).

Categories: Tigase Forums

Tigase server administration: RE: Web interface to Tigase server

Tigase XMPP Server Board - Wed, 04/15/2015 - 04:20

The issue (#2654) still was not resolved, sorry.

Categories: Tigase Forums

Tigase server administration: Is it possible to change the log level at runtime?

Tigase XMPP Server Board - Wed, 04/15/2015 - 01:11

Is it possible to change the log level at runtime?

for example next settings in init-properties:

--debug = server,db,muc,xmpp,http --debug-packages=com.services basic-conf/logging/tigase.db.level=SEVERE
Categories: Tigase Forums

Tigase server administration: RE: Web interface to Tigase server

Tigase XMPP Server Board - Tue, 04/14/2015 - 19:13

I got the same problem "When I click on 'Authenticate' the application does not proceed" with admin credentials (FullJID) when i visit the http://XXX:8080/ui/from remote. but it works via local browser.

Categories: Tigase Forums

Tigase server administration: RE: Too many elements in the user roster.. Warning

Tigase XMPP Server Board - Tue, 04/14/2015 - 06:10

Thank you Artur for the reply.
After reading your comment, I adjusted the memory in tigase.conf and the Warnings disappeared.

I used the following Linux command to get Heap memory parameters in the test server:
java -XX:+PrintFlagsFinal -version | grep HeapSize

I looked for the options MaxHeapSize (for -Xmx) and InitialHeapSize for -Xms

Categories: Tigase Forums

Tigase server administration: RE: How to enable only particular level of logs?

Tigase XMPP Server Board - Tue, 04/14/2015 - 00:27

Thanks, that makes sense,

so if I would like to track only SEVERE and WARNING then set to WARNING will do that

thanks

Categories: Tigase Forums

Tigase server administration: RE: --max-queue-size question

Tigase XMPP Server Board - Mon, 04/13/2015 - 17:43

I suggest to not adjust the setting unless you really need it. The default is set by Tigase based on available memory and it calculated to provide optimum performance with large buffer and avoid OOM errors in case of a bottleneck.

Categories: Tigase Forums

Tigase server administration: RE: How to enable only particular level of logs?

Tigase XMPP Server Board - Mon, 04/13/2015 - 17:41

Igor, as Wojciech said it is not possible but also not necessary. If you set logging level to FINEST it also includes all log records generated on higher levels (FINER, FINE, INFO, WARNING, SEVERE).

Categories: Tigase Forums

Tigase server development: RE: After aprox. 45 seconds connected the server send me unavailable p...

Tigase XMPP Server Board - Mon, 04/13/2015 - 17:39

This most likely happens when the client lost connections to the server. When the server discovers that the user disconnected one of his resources it generates presence unavailable on behalf of the user and sends it to all user's contacts and all user's other connections.

Categories: Tigase Forums

Tigase server administration: RE: Too many elements in the user roster.. Warning

Tigase XMPP Server Board - Mon, 04/13/2015 - 15:32

Apparently user's roster exceeded the maximum allowed size on your installation. The exception is thrown when there is an attempt to add a new contact to a roster when the roster is already at maximum size.

The roster maximum size is a dynamic value which depends on the memory available to the Tigase XMPP Server software. Here is the algorithm we use to calculate the maximum roster size:
private static int maxRosterSize = new Long(Runtime.getRuntime().maxMemory() / 250000L).intValue();

A solution to you would be to calculate the maximum size on your installation and ensure that you really require rosters with a bigger size. (maybe it is kind of a DOS attack on your service?)
If you really require large rosters on your system then you can increase amount of memory available to the Tigase server on your installation.

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