Tigase XMPP Server Board

Tigase server development: RE: Custom emoticon implementation

Wed, 03/25/2015 - 03:28

After quickly skimming through the specification it seems it's a client-side specification and it should be handled by Tigase just fine.

Categories: Tigase Forums

Tigase server development: RE: Tigase 7.0.0 S2SConnectionManager exception

Wed, 03/25/2015 - 02:02

So, you mean that hostname -f should be reachable via Internet?

Categories: Tigase Forums

Tigase server development: Custom emoticon implementation

Tue, 03/24/2015 - 23:31

Does Tigase-5.2.3 support XEP-0231?. If no, How can I implement Custom emoticon?. Please help to get an idea or share me if you have done any implementation for emoticon in chats.

Categories: Tigase Forums

Tigase server development: RE: Tigase 5.1.0 support of RFC 6120

Tue, 03/24/2015 - 17:34

Artur, thank you for taking the time to answer these questions.

Categories: Tigase Forums

Tigase server development: RE: Issue with AMP when enabling message carbon

Tue, 03/24/2015 - 16:19

Thank you for letting us know about the problem, I created a bug report for you: #2877

Categories: Tigase Forums

Tigase server development: RE: Tigase 7.0.0 S2SConnectionManager exception

Tue, 03/24/2015 - 16:09

You have to make sure your custom hostname has a correct DNS entry.

Categories: Tigase Forums

Tigase server development: RE: Tigase 7.0.0 S2SConnectionManager exception

Tue, 03/24/2015 - 14:20

Yes, I also got this point

but what is the right way to fix this?

Here is what I have:
1) Didn't have this issue with Tigase 5.2.0
2) Let's say our Tigase instance DNS is chat.my.com
3) The same value is in init.properties: --virt-hosts = chat.my.com
4) It doesn't work with custom hostname -f

Categories: Tigase Forums

Tigase server development: RE: Tigase 7.0.0 S2SConnectionManager exception

Tue, 03/24/2015 - 12:23

Unfortunately your solution will not work if you run Tigase in a cluster mode. In a cluster mode each server needs to have a distinct canonical hostname, and that hostname must be also different form any of vhosts you have.

Categories: Tigase Forums

Tigase server development: RE: Tigase 7.0.0 S2SConnectionManager exception

Tue, 03/24/2015 - 08:53

Thanks,

I did some changes around hostname settings.

Previously hostname -f command returned ip-10-222-235-20.ec2.internal
But now I changed this and it prints the same what I set in --virt-hosts -> chat.my.com

and looks like now I don't see that exception

Is it a right way how it should work?

Categories: Tigase Forums

Tigase server development: Issue with AMP when enabling message carbon

Tue, 03/24/2015 - 06:22

To implement message delivery options(single and double ticks) as like Whatsapp,I used to support XEP-0079 and XEP-0184. I achieved XEP-0184 without any issue. When I tried to get implement XEP-0079, I have faced the followings,
1.Message was not delivered to all the resources of recipient. Delivered to only one resource even I have enabled message-carbon.
2.Got an error message when the recipient in offline.

FYI, I am using tigase-message-archiving-1.0.1.jar for archiving messages
Tigase version 5.2.3

Request:
<message xmlns="jabber:client" from="550bc7a38acd14171215f3cb@192.168.1.94/opsbus_1427201770886" to="550bc7b08acd14171215f3ce@192.168.1.94" type="chat" id="1427201906165" isofflinemsg="false"> <body>Test mesage</body> <custom msgid="534870c5-fe61-4359-b3b4-2d6ea16edbd6" /> <active xmlns="http://jabber.org/protocol/chatstates" /> <request xmlns="urn:xmpp:receipts" /> <amp xmlns="http://jabber.org/protocol/amp" per-hop="true"> <rule condition="deliver" action="notify" value="stored" /> <rule condition="deliver" action="notify" value="direct" /> </amp> </message>

Response to sender:
<message xmlns="jabber:client" id="1427201906165" from="192.168.1.94" to="550bc7a38acd14171215f3cb@192.168.1.94/opsbus_1427201770886" isofflinemsg="false" type="chat"> <body>Test mesage</body> <custom msgid="534870c5-fe61-4359-b3b4-2d6ea16edbd6" /> <active xmlns="http://jabber.org/protocol/chatstates" /> <request xmlns="urn:xmpp:receipts" /> <amp xmlns="http://jabber.org/protocol/amp" status="notify" from="550bc7a38acd14171215f3cb@192.168.1.94/opsbus_1427201770886" to="550bc7b08acd14171215f3ce@192.168.1.94"> <rule condition="deliver" action="notify" value="direct" /> </amp> </message>

At receiver end:
<message xmlns="jabber:client" from="550bc7a38acd14171215f3cb@192.168.1.94/opsbus_1427201770886" to="550bc7b08acd14171215f3ce@192.168.1.94" id="1427202045173" isofflinemsg="false" type="chat"> <body>test message</body> <custom msgid="6fa40c07-a6bf-4d91-d7ac-a9b2d0d15d05" /> <active xmlns="http://jabber.org/protocol/chatstates" /> <request xmlns="urn:xmpp:receipts" /> <amp xmlns="http://jabber.org/protocol/amp" per-hop="true"> <rule condition="deliver" action="notify" value="stored" /> <rule condition="deliver" action="notify" value="direct" /> </amp> </message>

Please look at the response, it doesn't have resource id attached with "to".

Property file
--comp-class-6 = tigase.muc.MUCComponent --comp-class-5 = tigase.muc.MUCComponent --virt-hosts = 192.168.1.94 --user-db-uri = jdbc:mysql://localhost/tigasedb1?user=root&password=root --user-db = mysql --admins = admin@192.168.1.94 --comp-name-4 = message-archive --comp-name-3 = proxy config-type = --gen-config-def --comp-name-2 = pubsub --comp-name-6 = conference --comp-name-5 = channel --cluster-mode = false #--sm-plugins=+message-archive-xep-0136,-amp,-msgoffline,-message,+message-all --sm-plugins=+message-archive-xep-0136,amp,-msgoffline,-message --debug = server --comp-class-4 = tigase.archive.MessageArchiveComponent --comp-class-3 = tigase.socks5.Socks5ProxyComponent --comp-class-2 = tigase.pubsub.PubSubComponent # To save group chat message. conference/default_room_config/conference#roomconfig_persistentroom=true channel/default_room_config/channel#roomconfig_persistentroom=true --debug=server, xmpp.impl # To Enabling typing notification conference/muc-allow-chat-states[B]=true conference/message-filter-enabled[B]=false message-archive/archive-repo-uri=jdbc:mysql://localhost/tigasedb1?user=root&password=root sess-man/plugins-conf/message-archive-xep-0136/required-store-method=message sess-man/plugins-conf/message-archive-xep-0136/component-jid=message-archive@192.168.1.94 --amp-repo-uri=jdbc:mysql://localhost/tigasedb1?user=root&password=root sess-man/plugins-conf/amp/amp-jid=amp@192.168.1.94 --amp-security-level=NONE

Error when the recipient in offline

MsgRepository.storeMessage() WARNING: Problem adding new entry to DB: java.sql.SQLException: Field 'msg_type' doesn't have a default value at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3491) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3423) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1936) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2060) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2542) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1734) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2019) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1937) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1922) at tigase.server.amp.MsgRepository.storeMessage(MsgRepository.java:488) at tigase.server.amp.action.Store.execute(Store.java:129) at tigase.server.amp.AmpComponent.processPacket(AmpComponent.java:294) at tigase.server.AbstractMessageReceiver$QueueListener.run(AbstractMessageReceiver.java:1475)
Categories: Tigase Forums

Tigase server development: RE: Offline message not storing while using AMP plugin.

Tue, 03/24/2015 - 02:26

Please find the attached log file and help me to resolve this issue.
FYI, I enabled message-carbon protocol(XEP-0280) in order to that all the resources of receiver should get the message. Carbon works for sender.
Due to this integration with AMP, this carbon functionality doesn't work.

Categories: Tigase Forums

Tigase server development: RE: Offline message not storing while using AMP plugin.

Tue, 03/24/2015 - 02:11

You've provided to little details. Configuration looks ok, so my suggestion would be to track the message in Tigase logs while it's being processed. It could be helpful to enable debugging:
--debug=server,xmpp.impl

Categories: Tigase Forums

Tigase server development: RE: Offline message not storing while using AMP plugin.

Mon, 03/23/2015 - 21:59

This is my mistake, Sorry. I have set wrong database name in --amp-uri.

And One more thing i wanted to ask you, that If I using AMP and login user
A in two device and user B in one device. If user B send message to user A
these two devices are not getting sent message.

This problem is in If using AMP.

My properties are,
--sm-plugins = +message-archive-xep-0136, amp, -msgoffline, -message
--amp-repo-uri=jdbc:mysql://localhost/tigasedb1?user=root&password=root
sess-man/plugins-conf/amp/amp-jid=
--amp-security-level=NONE

Can U help this?

On Mon, Mar 23, 2015 at 3:31 PM, <> wrote:

Categories: Tigase Forums

Tigase server development: RE: Regarding bug fix #2693 target release

Mon, 03/23/2015 - 13:51

Vinoth Rajendran wrote:

Hi,
I am using Tigase server v5.2.3 and facing this issue #2693 right now. In what target release this bug is fixed?

The status of the ticket says it was fixed a month ago. To have the fix you need to switch to more recent version of the Tigase server software.

For group chat message delivery receipts, can I use XEP-0079 or can you suggest any other protocol?

Generally MUC does not allow for any extra payload to pass through the component. In Tigase case it depends on the MUC component configuration
You need to adjust the MUC configuration in order to let the extra payload get to the other side clients. However, in my opinion message delivery receipts are of a very little use in case of group chat. Because, if a user sends a message and there are 1,000 other users in the MUC room, the user can get 1,000 message delivery confirmations which seems kind of pointless. And what the client is supposed to do if there are only 995 message delivery receipts received?

Categories: Tigase Forums

Tigase server development: Regarding bug fix #2693 target release

Mon, 03/23/2015 - 03:55

Hi,
I am using Tigase server v5.2.3 and facing this issue #2693 right now. In what target release this bug is fixed?
For group chat message delivery receipts, can I use XEP-0079 or can you suggest any other protocol?

Categories: Tigase Forums

Tigase server development: RE: Offline message not storing while using AMP plugin.

Mon, 03/23/2015 - 03:01

Vinoth Rajendran wrote:

I am using Tigase 5.2.3 and my init.properties file attached below.

I have activated amp plugin.
While I send message to a offline user and when user comes online, its not displayed.

If user is offline, when I send message This exception is happening,

2015-03-20 19:56:29.180 [in_0-amp] MsgRepository.storeMessage() WARNING: Problem adding new entry to DB:
java.sql.SQLException: Field 'msg_type' doesn't have a default value

Have you, by any chance, tried to use newer version of Tigase at any point in time on the same database? It looks like you have - please remove offending column from the database to use older version of Tigase.

Categories: Tigase Forums

Tigase server development: RE: Offline message not storing while using AMP plugin.

Fri, 03/20/2015 - 16:19

It looks like you may have mismatched Tigase libraries version (use components in incompatible version with earlier Tigase version). Are you sure you use Tigase and all components from the installation package only?

Categories: Tigase Forums

Tigase server development: RE: Tigase 5.1.0 support of RFC 6120

Fri, 03/20/2015 - 15:40

Yes, this is supported for s2s connections, however, as far as I remember we added support for this in version 5.2.x.

Categories: Tigase Forums

Tigase server development: RE: Tigase 7.0.0 S2SConnectionManager exception

Fri, 03/20/2015 - 15:33

Most likely this is a result of misconfiguration of the network settings on the server, that is canonical hostname used by the server software and DNS pointing to the hostname. Sometimes if settings are not correct, the server recognizes the machine hostname as an external address and attempts to connect to it.

To help you with this we would need access to unedited copy of your logs (mainly a XMPP packet that triggered the event) and init.properties file.

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