Feed aggregator

Installation and maintenance: RE: Simple questions

Tigase XMPP Server Board - Tue, 07/26/2016 - 04:00

There is no support in Tigase XMPP Server for offline file transfer, even with plugins provided by us. We will work on implementation of XEP-0363 in task #4243 which should solve this issue.

Categories: Tigase Forums

Installation and maintenance: RE: Simple questions

Tigase XMPP Server Board - Mon, 07/25/2016 - 22:43

May be tigase has WebDav or Jabber Disk plugins support to resolve offline file transfer?

Categories: Tigase Forums

Installation and maintenance: RE: Can't get TLS working on HTTP API

Tigase XMPP Server Board - Sun, 07/24/2016 - 05:05

OK, thanks a lot for clarifying.
I'll wait for Tigase HTTP API 1.2.0 :-)

Categories: Tigase Forums

Installation and maintenance: RE: Can't get TLS working on HTTP API

Tigase XMPP Server Board - Sun, 07/24/2016 - 02:09

Tigase XMPP Server 7.0.4 ships and uses Tigase HTTP API in version 1.1.0. Support for configuration of SSL/TLS was added in Tigase HTTP API 1.2.0 and is not yet released as stable version.
This new version of Tigase HTTP API requires new version of Tigase XMPP Server (at least version 7.1.0, which should be released soon - for now only snapshot builds are available).

As for configuration it is wrong for version 1.1.0 as uses unsupported features, but it is also wrong for version 1.2.0 of HTTP API. It should look like this:
--comp-name-6=http --comp-class-6=tigase.http.HttpMessageReceiver http/http/server-class[S]=tigase.http.jetty.JettyStandaloneHttpServer http/http/ports[i]=8080,8081 http/http/8081/domain=mycompany.com http/http/8081/socket=ssl

First http in line is name of component and second http in line is part of property for this component. Also your needed to add 8081 to list of ports on which HTTP server should listen.
In this configuration we have plaintext http server on port 8080 and HTTPS server on port 8081.

Categories: Tigase Forums

Installation and maintenance: Can't get TLS working on HTTP API

Tigase XMPP Server Board - Sat, 07/23/2016 - 14:23

Hi
I'm trying to activate SSL/TLS on the HTTP API, but without any luck
Running Tigase 7.0.4

Here is the relevant part of my init.properties file:
--comp-name-6=http
--comp-class-6=tigase.http.HttpMessageReceiver
http/server-class[S]=tigase.http.jetty.JettyStandaloneHttpServer
http/http/ports[i]=8080
http/8081/domain=mycompany.com

What am I doing wrong ?

/Henrik

Categories: Tigase Forums

Installation and maintenance: RE: Missing initial presence packets

Tigase XMPP Server Board - Mon, 07/18/2016 - 02:48

Pankaj Sharma wrote:

While diagnostic that below configurations were missing in the application which restricts presence packet to be sent to offline users:

sess-man/plugins-conf/presence/skip-offline=false
sess-man/plugins-conf/presence/skip-offline-sys=false

Are those configuration options set when the problem manifests itself? Which version are you using? In the latest 7.1.0-SNAPSHOT presence plugin were split therefore those options may be ignored.

Please help me understand when the roster value is set to default and why it is not being assigned proper value though the user in the roster element has logged in to the application in past?

This information is stored in the user roster for all its contacts, therefore it's essential that contact's presence was received by the user (which implies, that the subscription also has to be correct between the two).
The value 10000 is the default for each RosterElement and is assigned when such object is created.

Also if there is any workaround the problem?

Please check the configuration and presence subscription.

Categories: Tigase Forums

Installation and maintenance: RE: jingle protocol support

Tigase XMPP Server Board - Sun, 07/17/2016 - 22:52

Yes! This is fixed my problem. Thanks for the support.

Categories: Tigase Forums

API and development: RE: Network disconnection detection

Tigase XMPP Server Board - Fri, 07/15/2016 - 12:30

Hi Mohammed,
Is the server detecting them at all?
I would have a look at the debug logs for xmpp to see where those packets go.

If you are using the nightly builds, you can set a connection watchdog that will disconnect inactive connections
details here: http://docs.tigase.org/tigase-server/snapshot/Administration_Guide/html/#watchdog
You can set some tighter tolerances and that will disconnect them.

Categories: Tigase Forums

Installation and maintenance: Missing initial presence packets

Tigase XMPP Server Board - Wed, 07/13/2016 - 11:20

Hi,

While troubleshooting a problem i stumbled upon a scenario where presence packets(in response to initial presence packet) were not being sent.

While diagnostic that below configurations were missing in the application which restricts presence packet to be sent to offline users:

sess-man/plugins-conf/presence/skip-offline=false
sess-man/plugins-conf/presence/skip-offline-sys=false

Upon some more troubleshooting it seems all the contacts in roster are present but the RosterElement.lastSeen is set to default value(10000) for some of the roster members.

Because this value is set to default the presence packets are not sent for these roster memebers as per the code below in RosterFlat.java

public Element getCustomChild(XMPPResourceConnection session, JID buddy) throws NotAuthorizedException, TigaseDBException {
RosterElement rel = getRosterElement(session, buddy);
if (rel != null && rel.getLastSeen() > RosterElement.INITIAL_LAST_SEEN_VAL) {
String stamp;
synchronized (formatter) {
stamp = formatter.format(new Date(rel.getLastSeen()));
}
return new Element("delay", new String[]{"stamp", "xmlns"}, new String[]{stamp, "urn:xmpp:delay"});
}
return null;
}

Please help me understand when the roster value is set to default and why it is not being assigned proper value though the user in the roster element has logged in to the application in past? Also if there is any workaround the problem?

Categories: Tigase Forums

API and development: Network disconnection detection

Tigase XMPP Server Board - Mon, 07/11/2016 - 05:42

hi all,

I am using the tigase 7.0.4. I am facing a problem with the server not able to detect a connection loss from a user once his network is disconnected...he will be shown as online for other users...and the messages sent to this user during this time is also not saved as an offline message.is this the normal behavior or am i doing something wrong.

Please help
Thank you

Categories: Tigase Forums

Tigase XMPP Client Library - Tigase JaXMPP Client v3.1.2 Release

Tigase Development News - Fri, 07/08/2016 - 09:01

A new version of Tigase XMPP Client Library has been released. The current version is v3.1.2.

Please see http://www.tigase.net/blog-entry/tigase-jaxmpp-client-v312-release for release notes.

API and development: RE: Some questions about DrupalWPAuth.

Tigase XMPP Server Board - Mon, 07/04/2016 - 07:10

Kelly Kuang wrote:

2. In Drupal 7.43, it is no longer use MD5 to generate the password digest. Although the input password is correct, the (1) value never equal the (2) value in DrupalWPAuth#plainAuth().
What can I do to solve value not equal problem? Do I need to implement my own password function according to Drupal password encode function and replace to DrupalWPAuth?

Unfortunately DrupalWPAuth supports only older versions of Drupal (or those with the new hashing disabled). You can either change the hashing used in Drupal or implement appropriate hashing in DrupalWPAuth.

Categories: Tigase Forums

API and development: RE: Too long resource

Tigase XMPP Server Board - Mon, 07/04/2016 - 07:07

Thank you, I've commit a fix to the repository.

Categories: Tigase Forums

API and development: RE: Too long resource

Tigase XMPP Server Board - Sun, 07/03/2016 - 19:17

sorry for reply so late!

Meothed init(Map<String, Object> settings) in BindResource.java called when component added or removed via web console(xx:8090/ui/, "Manage active server components"),
@Override public void init(Map<String, Object> settings) throws TigaseDBException { int hostnameHash = Math.abs( DNSResolver.getDefaultHostname().hashCode() ); // Init plugin configuration if (settings.get(DEF_RESOURCE_PREFIX_PROP_KEY) != null) { resourceDefPrefix = hostnameHash + "-" + settings.get(DEF_RESOURCE_PREFIX_PROP_KEY).toString(); } else { resourceDefPrefix = hostnameHash + "-" + resourceDefPrefix; } }

resourceDefPrefix accumulate every time when comp changed , It makes resource longer.

Categories: Tigase Forums

API and development: Some questions about DrupalWPAuth.

Tigase XMPP Server Board - Sat, 07/02/2016 - 00:06

I want to change AuthRepository implement from TigaseCustomAuth to DrupalWPAuth.
But DrupalWPAuth#plainAuth() return false.

I confirm that DrupalWPAuth connect to Drupal DB successfully. And DrupalWPAuth can get the user info from Drupal DB.

In DrupalWPAuth#plainAuth() I find that:
(1) calculate the input password MD5 hex digest.
(2) get the user password digest(not plain text) from Drupal DB.
(3) verify above two values.

My questions:
1. The DrupalWPAuth#plainAuth() is deprecated. The otherAuth() is preferred. But in AuthRepoPlainCallbackHandler#handleVerifyPasswordCallback(), it is hardcode to use "PROTOCOL_VAL_NONSASL" not "PROTOCOL_VAL_SASL".

This property will control the AuthRepository use plainAuth.
I know that it call repo.otherAuth() in AuthRepoPlainCallbackHandler#handleVerifyPasswordCallback(). But inside the repo.otherAuth(), it still call plainAuth() according to the AuthRepository.PROTOCOL_VAL_NONSASL. (I have checked the code both in TigaseCustomAuth and DrupalWPAuth.)

Is there any configs to control the property in handleVerifyPasswordCallback()?
Is the DrupalWPAuth#saslAuth never be called?

2. In Drupal 7.43, it is no longer use MD5 to generate the password digest. Although the input password is correct, the (1) value never equal the (2) value in DrupalWPAuth#plainAuth().
What can I do to solve value not equal problem? Do I need to implement my own password function according to Drupal password encode function and replace to DrupalWPAuth?

Categories: Tigase Forums

API and development: RE: Too long resource

Tigase XMPP Server Board - Tue, 06/28/2016 - 03:44

Hic cup wrote:

when comp(eg:http) add,edit and remove via web console,this mothed will be called, and resourceDefPrefix longer (eg:100@domain/1752483901-1752483901-1752483901-1752483901-tigase-279)

Can you rephrase it to make it more clear? Ideally with steps to reproduce and both expected result and (what you consider) wrong result?

Categories: Tigase Forums

API and development: Too long resource

Tigase XMPP Server Board - Mon, 06/27/2016 - 23:59

hi!guys.
My client login and resource create by server.

In BindResource.java Mothed init(Map<String, Object> settings)
resourceDefPrefix = hostnameHash + "-" + resourceDefPrefix;

when comp(eg:http) add,edit and remove via web console,this mothed will be called, and resourceDefPrefix longer (eg:100@domain/1752483901-1752483901-1752483901-1752483901-tigase-279)

Categories: Tigase Forums

Installation and maintenance: RE: Pending SM messages lost during shutdown

Tigase XMPP Server Board - Mon, 06/27/2016 - 12:00

Thanks for the insightful info! Looking forward to an even better shutdown handling.

Categories: Tigase Forums

Installation and maintenance: RE: Pending SM messages lost during shutdown

Tigase XMPP Server Board - Mon, 06/27/2016 - 08:03

Messages which are in processing queue and in session management queues may be lost during server shutdown. This is caused by the fact that currently shutdown is initiated termination signal being sent to server. This all is done by design to allow fast shutdown and later fast startup which is needed during server restart.

Yes, message loss can be caused by that, however message processing and delivery should be fast so it is rather hard to loss message due to that.

StreamManagement is responsible for queuing packets sent to client until they are confirmed as delivered. Right now this messages are kept in memory until connection is dropped, stream is resumed or packets are confirmed as delivered. So server shutdown may cause drop of this messages as well.

We will work on improvements to message delivery and graceful server shutdown in version 7.2.0. We already started by sending stream termination to clients when server will be stopped which will trigger message redelivery from stream resumption queue.

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 4 days 13 hours 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 5 days ago
Back to Top