Tigase, BOSH, JSJaC: invalid response (12152)

2 posts / 0 new
Last post
Anonymous
Tigase, BOSH, JSJaC: invalid response (12152)

I have a Tigase server with clients connecting to it via JSJaC over HTTPS. I have about 1/6 of the users reporting "invalid response (12152)" immediately upon connection and repeatedly thereafter, but can send and receive messages. Based on the timing, it would seem to be the BOSH connection maintenance. This seems as though it could be webserver configuration related, so I've included it below. As you can see, I used your recommended config complete with comments and adapted it slightly. I would also note, these are corporate users that could very well have proxy and/or firewalls affecting traffic in some way. Any ideas what could cause this error?


DocumentRoot /mnt/myuser/myapp/web
ServerName mysite.com
ServerSignature off

# I think this is important for Tigase Bosh component which is NOT
# HTTP-1.1 compliant server, it just pretends to be HTTP server and
# has a vey basic HTTP implementation
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1

Options +Indexes +Multiviews
AllowOverride All
Order allow,deny
Allow from all
# This section is important for GWT based applications
# Switch web browser and proxy caching for selected files.

FileETag None
Header unset ETag
Header set Cache-Control "max-age=0, no-cache, no-store, private"
Header set Pragma "no-cache"
Header set Expires "0"

AllowOverride All
Order allow,deny
Allow from all

Options ExecCGI FollowSymLinks
AddDefaultCharset UTF-8
AddHandler application/x-httpd-php .php .js
ProxyTimeout 600
RewriteEngine on
RewriteRule /msg http://mysite.com:5280/http-bind/ [P]

allow from all
Options +Indexes

SSLEngine on
SSLCertificateFile /etc/apache2/ssl/mysite.com/mysite_com.crt
SSLCertificateKeyFile /etc/apache2/ssl/mysite.com/myserver.key
ErrorLog /mnt/myuser/logs/apache2/https.log
LogLevel notice

Application: 

I am afraid, without a good research it is impossible to tell what is going on. How many online users do you have?
This may be something related to operating system configuration where the HTTP proxy works. If you use any Unix/Linux based system check maximum number of opened files set for the HTTP proxy user, check also number of TCP/IP ports available to the machine.
Check system logs if there is any issue with traffic throttling. Sometimes there is kind of firewalling system installed which may "think" machine is under DOS attack and tries to block some traffic. Also Selinux settings may affect the service.
Here are 2 articles worth reading:

  1. Linux settings for high load systems
  2. Basic system checks

I hope this helps.