bosh

502 Proxy Error with BOSH

Submitted by Anonymous on Mon, 2010-08-30 18:40
::

I am using Tigase with BOSH proxied through Apache. The problem is, I get intermittent 502 Proxy Errors. Has anyone seen this before?

MUC - Managing Discussion History does not work.

Submitted by Anonymous on Mon, 2010-08-16 17:32
::

Hi all.

I'm using Tigase Server to manage XMPP stranzas sent from a web client (JSJac and Strophe) through Bosh. I'm sending a presence stranza with this specific History manage attribute:

<history maxchars='0'/>

According to the XEP-0045 Multi-User Chat specification (http://xmpp.org/extensions/xep-0045.html#enter-managehistory), the XMPP server should not return any history messages at all if you specify the maxchars='0' attribute, but the problem is that I keep receiving all the history messages even if don't want to get them.

BOSH client hanging on starttls

Submitted by Anonymous on Sat, 2010-04-24 00:30
::

Hi,

I'm trying out BOSH and the client using ag-XMPP gets as far as requesting a starttls like so:

<starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls" />

The server never replies and shows this on the command line output:


jvm 1 | 2010-04-23 16:12:57 ClientConnectionManager.processCommand()
WARNING: Can't find sevice for STARTTLS command:
from=null, to=null, data=

Clustering and BOSH

Submitted by Anonymous on Wed, 2010-04-21 22:05
::

Hi,

In the clustering presentation from 2008 here: http://www.tigase.org/cluster-presentation it is specifically said that BOSH is not supported in clustering. Is this still true? If it is, in what way is BOSH not supported? Can we not use BOSH at all in a clustered set-up?

Also in the presentation there was mention about having "good db clustering". Is there a specific way we have to handle the organize the database in order for it to work with clustered Tigase?