Tigase XMPP Server Board

Tigase server development: RE: JID escaping?

Tue, 10/14/2014 - 21:57

There is no JID in non-SASL auth:

<iq type='set' id='auth2'> <query xmlns='jabber:iq:auth'> <username>bill</username> <password>Calli0pe</password> <resource>globe</resource> </query> </iq>
Categories: Tigase Forums

Tigase server administration: RE: Installation issue

Tue, 10/14/2014 - 10:54

Make sure the account admin@localhost is already a registered account on the Tigase server (so you can correctly login) and make also sure the account is listed as an admin account in the Tigase server init.properties file.

Categories: Tigase Forums

Tigase server development: RE: JID escaping?

Tue, 10/14/2014 - 10:46

There were many changes in the authentication code between 5.0 and 5.2 so it is likely it affects you. We are looking into this and someone from our team will respond shortly. By the way, if you are upgrading, I suggest to use either 5.2.1 or 5.2.2 version with the most recent fixes.

Categories: Tigase Forums

Tigase server development: JID escaping?

Tue, 10/14/2014 - 09:08

Hi,

I am trying to upgrade from Tigase 5.0.x to Tigase 5.2.0.
We are very pleased with how Tigase 5.0.x works but we thought it was time to upgrade.
I am having problem with Authentication and the @ sign in the JID. Otherwise it works better.
As an example with domain test@com and email as username joe@email.
That would be joe@ and from my understanding and http://www.xmpp.org/extensions/xep-0106.html it should be escaped.
So I send joe'\40'. But Tigase does not seem to like this?
In my example Tigase fails at JabberIqAuth:
BareJID user_id = BareJID.bareJIDInstance(user_name, session.getDomain().getVhost().getDomain());

Should it work? Any other suggestion?
Can I bypass this?

Categories: Tigase Forums

Tigase server administration: RE: Monitoring component (muc)

Tue, 10/14/2014 - 06:43

I thought about it, just wanted to check. Thank you.

Categories: Tigase Forums

Tigase server administration: RE: Installation issue

Tue, 10/14/2014 - 06:07

I just started to use tclmt for debugging my server.

I have also attached the error message from tclmt.

Categories: Tigase Forums

Tigase server administration: RE: Installation issue

Tue, 10/14/2014 - 04:02

Thanks for the immediate reply Wojciech.

I also tried using Pidgin to connect to the server.

The description of errors from Pidgin are attached below.

Categories: Tigase Forums

Tigase server administration: RE: Installation issue

Tue, 10/14/2014 - 03:43

Given that you are able to connect using telnet then it's most likely issue with the smack library or usage therof. Please try connecting using regular client, like Psi or Pidgin. If everything is ok then the issue is related to smack library and further questions should be asked in their forums.

Categories: Tigase Forums

Tigase server administration: RE: can't load schema:specified key was too long

Tue, 10/14/2014 - 03:38

This is related to the changes in MySQL 5.6 and new limits.

With the release of MySQL 5.6 there were a few changes to the defaults used by the database server mostly related to default engine which entails change in defaults regarding length of index key limits. This version switched from MyISAM to InnoDB (v. 5.1: default-storage-engine vs 5.6: default-storage-engine) and then Limits on InnoDB Tables for 5.1 and 5.6. The result in default configuration is the limitation of 767 bytes for index key prefix which is not met by Tigase schema because it defaults to using UTF8 for storage and while we define key length as 765 characters, because of using unicode (in case of MySQL this translates to 3-4bytes per character) we cross the maximum key length limitation.

In order to still be able to use such indexes a following options needs to be included in [mysqld] section of MySQL configuration (most likely, but not limited to, one of the following files: /etc/my.cnf, /etc/mysql/my.cnf, /usr/local/mysql/etc/my.cnf, ~/.my.cnf):
innodb_large_prefix=true innodb_file_format=barracuda innodb_file_per_table=true

The problem has been also addressed in Tigase, but this will be included in version 5.3.0 (and new nightlies of such).

Categories: Tigase Forums

Tigase server administration: Installation issue

Tue, 10/14/2014 - 00:15

Hi

I am trying to setup Tigase on my local machine following the guide : https://projects.tigase.org/projects/tigase-server/wiki/Quickstart

I am using pidgin as well as Spark as my XMPP client.

Server Details:

1. Domain : localhost
2. Port : 5223
Username and password are of the default admin user.

The error displayed by the smack client logs:

WARNING: Exception in Login:
Connection failed. No response from server.:
at org.jivesoftware.smack.PacketReader.startup(PacketReader.java:119)
at org.jivesoftware.smack.XMPPConnection.initConnection(XMPPConnection.java:568)
at org.jivesoftware.smack.XMPPConnection.connectUsingConfiguration(XMPPConnection.java:527)
at org.jivesoftware.smack.XMPPConnection.connect(XMPPConnection.java:953)
at org.jivesoftware.LoginDialog$LoginPanel.login(LoginDialog.java:1009)
at org.jivesoftware.LoginDialog$LoginPanel.access$1200(LoginDialog.java:219)
at org.jivesoftware.LoginDialog$LoginPanel$4.construct(LoginDialog.java:730)
at org.jivesoftware.spark.util.SwingWorker$2.run(SwingWorker.java:141)
at java.lang.Thread.run(Unknown Source)
java.io.EOFException: input contained no data
at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3003)
at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
at org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:325)
at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:43)
at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:70)
Oct 14, 2014 12:32:39 PM org.jivesoftware.spark.util.log.Log warning
WARNING: Exception in Login:
Connection failed. No response from server.:
at org.jivesoftware.smack.PacketReader.startup(PacketReader.java:119)
at org.jivesoftware.smack.XMPPConnection.initConnection(XMPPConnection.java:568)
at org.jivesoftware.smack.XMPPConnection.connectUsingConfiguration(XMPPConnection.java:527)
at org.jivesoftware.smack.XMPPConnection.connect(XMPPConnection.java:953)
at org.jivesoftware.LoginDialog$LoginPanel.login(LoginDialog.java:1009)
at org.jivesoftware.LoginDialog$LoginPanel.access$1200(LoginDialog.java:219)
at org.jivesoftware.LoginDialog$LoginPanel$4.construct(LoginDialog.java:730)
at org.jivesoftware.spark.util.SwingWorker$2.run(SwingWorker.java:141)
at java.lang.Thread.run(Unknown Source)

I am however able to telnet to ports 5222, 5223.

Am I missing something here ?

Categories: Tigase Forums

Tigase server administration: can't load schema:specified key was too long

Mon, 10/13/2014 - 18:19

during I install tigase xmpp server 5.2.0 by GUI,this problem happened.
first i thought maybe the character of myschema not matched,so I tried alter database set tigasedb character set latin 1,and tried checking again,but didn't work.
(I'm using mysql server 5.6 on Windows 8)

Categories: Tigase Forums

Tigase server development: RE: Impossible happened

Mon, 10/13/2014 - 13:35

Do you get a response from the server to your ping requests?
I think this happens, because SM receives packets for which there is no user session, so it does not know how to respond to the request. This is kind of a special case for which we could/should write a fix.

Categories: Tigase Forums

Tigase server administration: RE: Monitoring component (muc)

Mon, 10/13/2014 - 13:28

You can get Tigase statistics which include metrics for individual components. These show the traffic on each component, etc... So this is some indication that a component is more or less working but it does not give you a guarantee that ell functions are working correctly. To be sure you would need more sophisticated monitoring, such as a command line client/bot which connects to the Tigase and tries to interact with the component (MUC) such as creating a new room, joining room, sending messages, etc....

Categories: Tigase Forums

Tigase server administration: RE: Monitoring component (muc)

Mon, 10/13/2014 - 02:51

I need to know that the component is working.

Categories: Tigase Forums

Tigase server administration: RE: Monitoring component (muc)

Mon, 10/13/2014 - 02:32

What do you mean by 'monitor'? There is a variety of metrics available for all components and they can be accessed by a number of means (xmpp, jmx, etc). Please be more specific what you would like to achieve.

Categories: Tigase Forums

Tigase server administration: Monitoring component (muc)

Mon, 10/13/2014 - 02:24

Dear experts.

Is it possible to monitor the individual components of tigase? I'm interested in muc.
(It means using of tigase functionality)

Categories: Tigase Forums

Tigase server development: Impossible happened

Sun, 10/12/2014 - 23:00

Hi

I got these in the log:
2014-10-13 07:54:56.966 [in_43-sess-man] SessionManager.processPacket() INFO: Impossible happened, please report to developer packet: from=null, to=sess-man@tigase.cego.dk, DATA=<iq xmlns="jabber:client" id="EeW" to="cego.dk" type="get" from="services.cego.dk"><ping xmlns="urn:xmpp:ping"/></iq>, SIZE=117, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=get, connection: XMPPResourceConnection=[user_jid=sess-man@tigase.cego.dk, packets=1, connectioId=null, domain=tigase.cego.dk, authState=NOT_AUTHORIZED, isAnon=false, isTmp=false].

Everything seems to work thou.
'services.cego.dk' is a XEP-0114 based component and it sends XMPP ping packets every ten seconds. Each time a line like the above is logged.

Is that a bug?

Categories: Tigase Forums

MongoDB discussion: RE: [Compilation Error] error: package Repository does not exist

Sun, 10/12/2014 - 22:25

Thanks that worked like charm.

Thanks Artur Hefczyc for explaining my mistake as well.

Categories: Tigase Forums

Tigase server development: RE: Chat bot as component

Fri, 10/10/2014 - 12:10

When you send a message from your component you have to set "form" attribute in the stanza. Also you need to correct addressing for the component. It cannot be in form: test-component@domain, where domain is the same domain which is served by the session manager (domain for your XMPP server). This causes confusion in the stanza routing. You should use: text-component.domain as your component address in "from" and "to" attributes.

Categories: Tigase Forums

Tigase server administration: RE: Jaxmpp BOSH Client: Problem with event listeners

Fri, 10/10/2014 - 11:51

I think this has been answered in ticket #2336. Please let me know if not.

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

  • If you need a stable communication with the world Tigase Messenger is for you. Test it. http://t.co/CZeskBZgon 15 hours 23 min ago
  • RT @jitsinews: Just ran a few tests with Wojciech and Eric. @tigase now officially supports Jitsi Meet and Jitsi Videobridge in latest nigh… 3 days 6 hours ago
Back to Top