Tigase XMPP Server Board

Tigase server administration: RE: Tigase XMPP configuration doubt.

Wed, 05/20/2015 - 21:12

Erik, we can do the modification to Tigase to add implementation for "MAY" part, however, there are different options for you to consider. I do not know too much about your system and why you actually need presence information, but querying for presence of a device using probe might be very inefficient, especially if you have more than 1M connected devices.

It may take long time and generate huge traffic to request presences of all connected devices. And then, once a new device is connected or existing device disconnects you are not up to date with the presence change. To refresh presences you would have to send presence probe to 1M devices again and do it periodically. And what if you have 10M or even 100M devices. It may not scale well/at all.

If you need a device presence on demand, from time to time, then using probe might make sense.

  1. Another option would be to use Tigase's built-in feature which we call presence forwarding. It allows you to configure Tigase to forward all the presence changes at the time when they happen to a given XMPP address. This allows you to aggregate and maintain presence status in real time. It may still generate quite high traffic between the server and the XMPP entity which has to aggregate presence status but should be doable.
  2. Yet another option would be to integrate some of your logic directly within Tigase server which can provide you presence information in real time through the API. That would be the most efficient from the performance point of view and most effective from the resource consumption point of view.
Categories: Tigase Forums

Tigase server administration: RE: How to connect to Tigase server on aws

Wed, 05/20/2015 - 19:39

Hi Wojcieh

Thanks, we were finally able to get the clients connected to tigase server
on aws, issue was related to root permission.

We are able to register users onto tigase server on aws and on the derby
database we see the users being added but with account status as -1.
When the user tries login in , client gets disconnected with this error
message "server closed the connection".

I have attached a brief log snapshot when I fire my client connection to
tigase server running on aws.

Thanks
Mayank

On Wed, May 20, 2015 at 8:28 AM <> wrote:

Categories: Tigase Forums

MongoDB discussion: How to see message archive?

Wed, 05/20/2015 - 15:07

Hi,
I configure mongodb and tigase it worked but where is my message?How can see message log?

Categories: Tigase Forums

Tigase server administration: RE: Tigase XMPP configuration doubt.

Wed, 05/20/2015 - 08:17

Hi Wojciech

Look, i think that we found the problem that we has it .

https://xmpp.org/rfcs/rfc6121.html#presence-probe-inbound

Upon receiving a presence probe to the contact's bare JID from the
user's server on behalf of the user, the contact's server MUST reply
as follows:

1. If the contact account does not exist or the user's bare JID is
in the contact's roster with a subscription state other than
"From", "From + Pending Out", or "Both" (as explained under
Appendix A), then the contact's server SHOULD return a presence
stanza of type "unsubscribed" in response to the presence probe
(this will trigger a protocol flow for canceling the user's
subscription to the contact as described under Section 3.2;
however, this MUST NOT result in cancellation of a subscription
pre-approval as described under Section 3.4). Here the 'from'
address MUST be the bare JID of the contact, since specifying a
full JID would constitute a presence leak as described in
[XMPP-CORE]. CS: &lt;presence from=''
id='xv291f38'
to=''
type='unsubscribed'/> ” However, if a server receives a presence probe from a configured
domain of the server itself or another such trusted service, it MAY
provide presence information about the user to that entity.”

It’s the MAY part we want them to implement. Otherwise, we would have to subscribe to presence from all devices, which would be not only difficult to maintain, but it would not scale well, increase amount of unwanted communication, and it would also make it possible for client to reject (willfully, or because of program error/omission), which would make readout of the device impossible from the portal.

Can you implement the MAY part please ?

Best Regards and thanks for your help

-----Mensaje original-----
De: [mailto:]
Enviado el: martes, 19 de mayo de 2015 2:22
Asunto: [Tigase XMPP Server - Tigase server administration - msg5036] RE: Tigase XMPP configuration doubt.

Categories: Tigase Forums

Tigase server administration: RE: PubSub Node Configuration

Wed, 05/20/2015 - 08:12

I may have found the issue.
I noticed its replying with text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" as feature not implemented

Looking at server console -- its not loading that plugin (see below) is that normal?

Loading plugin: session-close=4:37865 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: session-open=4:37865 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: default-handler=4:37865 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: jabber:iq:auth=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: urn:ietf:params:xml:ns:xmpp-sasl=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: urn:ietf:params:xml:ns:xmpp-bind=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: urn:ietf:params:xml:ns:xmpp-session=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: jabber:iq:roster=4:37865 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: jabber:iq:privacy=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: jabber:iq:version=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: http://jabber.org/protocol/stats=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: vcard-temp=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: http://jabber.org/protocol/commands=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: jabber:iq:private=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: urn:xmpp:ping=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: presence=4:37865 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: disco=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: amp=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: message-carbons=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: message-archive-xep-0136=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: jabber:iq:register=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: msgoffline=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)
Loading plugin: pep=2:75730 ... , version: 7.0.1-b15/4d8a351c (2015-04-19/09:43:19)

Categories: Tigase Forums

Tigase server development: RE: Plugins are not receiving all the messages

Wed, 05/20/2015 - 08:05

Oh my ! This is what I was most fearing... thanks for the clue !
But now I have a problem: I need to forward that message to a component: I was sure that the admin@ was always online, so I made a plugin to intercept the message and forward it to the component.

How can I implement the same behavior now ? if the recipient will not be online (and it is most likely) the packet won't be processed at all... what would you suggest ?

Thanks in advance,
Luca

Categories: Tigase Forums

Tigase server administration: RE: PubSub Node Configuration

Wed, 05/20/2015 - 08:03

We are on version 7.0.1

Create Node response (obfuscated):

<iq xmlns="jabber:client" id="e250hqtj0p" from="pubsub.mydomain.com" to="/303225431-tigase-1996" type="result">
<text>Created in 166 ms</text>
</iq>

I can also see the node on DB.

Request (obfuscated):

<iq id="lul15j24ce" type="get" to="pubsub.mydomain.com">
<pubsub xmlns="http://jabber.org/protocol/pubsub#owner">
<configure node="node_name_aaa" />
</pubsub>
</iq>

Response (obfuscated):

<iq xmlns="jabber:client" id="lul15j24ce" to="/9822424-tigase-2112" from="pubsub.mydomain.com" type="error">
<pubsub xmlns="http://jabber.org/protocol/pubsub#owner">
<configure node="node_name_aaa" />
</pubsub>
<error code="501" type="cancel">
<feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" />
<text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" lang="en">Feature not supported yet.</text>
</error>
</iq>

Not understanding why this is happening

Categories: Tigase Forums

Tigase server administration: RE: PubSub Node Configuration

Wed, 05/20/2015 - 07:52

Only modifications that were made are to MessageAmp.java in order to support push notifications (will be in plugin form in the future) - this shouldnt affect pubsub as far as I am aware.

The only difference I can see between what I'm sending and the example you provided is that you did not use the "from=" child within iq element.
I will try to remove "from" from my client and see if its working - will update shortly.

Categories: Tigase Forums

Tigase server development: RE: Plugins are not receiving all the messages

Wed, 05/20/2015 - 07:44

There was a change in how packets are processed in Tigase XMPP Server in 7.x release in which SessionManager preprocesses messages and if it finds AMP rules then it forwards this stanzas for processing by AMP component.
So in first case user[from=amp@domain.net, to=sess-man@domain.net, this entry is correct as most propably SessionManager forwarded packet to AMP component for processing and now you received response from AMP component after processing.

Categories: Tigase Forums

Tigase server administration: RE: User hangs in memory

Wed, 05/20/2015 - 07:21

Julia Zashchitina wrote:

1) As shown in the attached log file, other users were able to connect to Tigase server and add-user or change-password scripts for them worked normally. Password for this users was changed in database as well, so db connection was successful.

If still reproducible - can you wrap the add-user/change-user-passwords scripts in try/catch (after imports) and share resulting stacktrace?

Categories: Tigase Forums

Tigase server development: RE: Plugins are not receiving all the messages

Wed, 05/20/2015 - 07:01

Well OK, but I send the message directly from admin@ to user@. Not that I want to find someone or something to blame, but could this be a problem in amp message handling ?
Or you see any reason for this to happen ? No message is sent directly to amp component, and from what you write, this is not an expected behavior.

Does this make any sense to you / rings any bell ?

All the best,
Luca

Categories: Tigase Forums

Tigase server development: RE: Plugins are not receiving all the messages

Wed, 05/20/2015 - 06:46

OK, one note - in first case packet is user[from=amp@domain.net, to=sess-man@domain.net, - note the from - it's from AMP component so it looks, that for some reason the packet was forwarded to AMP component.

Categories: Tigase Forums

Tigase server administration: RE: PubSub Node Configuration

Wed, 05/20/2015 - 06:39

Have you made any modifications anywhere in the server?

We are not able to reproduce the issue:
<iq type='get' to='pubsub.tigase.org' id='conf1'> <pubsub xmlns='http://jabber.org/protocol/pubsub#owner'> <configure node='w1'/> </pubsub> </iq> <iq from="pubsub.tigase.org" type="result" id="conf1" to="wojtek@tigase.org/atlantis/city/psi+"> <pubsub xmlns="http://jabber.org/protocol/pubsub#owner"> <configure node="w1"> <x xmlns="jabber:x:data" type="form"> …

Categories: Tigase Forums

Tigase server administration: RE: How to connect to Tigase server on aws

Wed, 05/20/2015 - 05:27

Mayank Maheshwari wrote:

Hi Tigase Gurus,

We are very new to Tigase and been trying to install it on AWS ( Amazon cloud) and connect to it over internet.
Unfortunately our xmpp client (pidgin/psi) is not being able to connect to the tigase server.

We tried connecting the client using domain name given to tigase server say xyz.com as well as ip address we use to log into our aws box ( ssh -i some.pem ubuntu@ip-address ), but none work.

Where do you specify it in the client? As the connection host?

If you are using domain name and JID you should configure SRV records for your domain.

When I try pinging that aws box with the provided ip-address, i see 100% messages being transfered.

Can you telnet any of Tigase ports (5222, 5223, etc) from the internet?

Categories: Tigase Forums

Tigase server administration: RE: PubSub Node Configuration

Wed, 05/20/2015 - 04:56

Yes I have, these are the only two lines for pubsub:

--comp-class-2 = tigase.pubsub.cluster.PubSubComponentClustered
--comp-name-2 = pubsub

I am able to create new nodes, just not able to GET configuration.

Categories: Tigase Forums

Tigase server administration: RE: PubSub Node Configuration

Wed, 05/20/2015 - 03:35

Yes, Tigase PubSub component support configuration of the node.Have you enabled pubsub component in the configuration?

Categories: Tigase Forums

Tigase server development: RE: how to slove Queue overflow and sessionmanager packet is to big

Wed, 05/20/2015 - 03:30

Not necessarily. You should retrieve full server statistics and check statistics of all plugins.

Categories: Tigase Forums

Tigase server development: RE: Plugins are not receiving all the messages

Wed, 05/20/2015 - 01:53

Just to integrate the information, if I send a message without AMP, the plugin works as expected:

2015-05-20 08:18:02.146 [Validity Queue Worker 0] MyPlugin.process() SEVERE: I am processing a packet from admin@domain.net to user@sub.domain.net in session for user admin[from=c2s@domain.net/172.31.18.86_5222_2.228.102.101_47566, to=sess-man@domain.net, DATA=<message to="user@sub.domain.net" id="ac3fa" from="admin@domain.net/Server-1" xmlns="jabber:client"> 2015-05-20 08:18:02.148 [Validity Queue Worker 0] MyPlugin.process() SEVERE: I am processing a packet from admin@domain.net to user@sub.domain.net in session for user user[from=sess-man@domain.net, to=sess-man@domain.net, DATA=<message to="user@sub.domain.net" id="ac3fa" from="admin@domain.net/Server-1" xmlns="jabber:client">

Maybe this further information can help you in finding out if something is going wrong

All the best
Luca

Categories: Tigase Forums

Tigase server administration: How to connect to Tigase server on aws

Tue, 05/19/2015 - 19:54

Hi Tigase Gurus,

We are very new to Tigase and been trying to install it on AWS ( Amazon cloud) and connect to it over internet.
Unfortunately our xmpp client (pidgin/psi) is not being able to connect to the tigase server.

We tried connecting the client using domain name given to tigase server say xyz.com as well as ip address we use to log into our aws box ( ssh -i some.pem ubuntu@ip-address ), but none work.
When I try pinging that aws box with the provided ip-address, i see 100% messages being transfered.

Can someone pls guide us or provide us with some documentation/forum threads related to tigase issue on aws.
Closest that I found to our issue is here https://projects.tigase.org/issues/2043.

Thanks

Categories: Tigase Forums

Tigase server administration: PubSub Node Configuration

Tue, 05/19/2015 - 07:17

Hi Guys,

Will appreciate any assistance you can provide with this issue.

According to XEP-0060 http://xmpp.org/extensions/xep-0060.html#owner-subscriptions-retrieve
I should be able set and get node configuration as follows:

<iq type='get'
from='/elsinore'
to='pubsub.shakespeare.lit'
id='config1'>
<pubsub xmlns='http://jabber.org/protocol/pubsub#owner'>
<configure node='princely_musings'/>
</pubsub>
</iq>

The problem is, when im sending this packet I get the following reply (user and domain obfuscated):
Feature not supported yet.

<iq xmlns="jabber:client" id="l0tez869gt" to="user@domain/9822424-tigase-2068" from="pubsub.domain" type="error">
<pubsub xmlns="http://jabber.org/protocol/pubsub#owner">
<configure node="node_name_aaa" />
</pubsub>
<error code="501" type="cancel">
<feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" />
<text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" lang="en">Feature not supported yet.</text>
</error>
</iq>

My question is - is this a configuration issue, or do you truly not support this impl?

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