Kommentare zu: JSJaC v1.3.2 released http://blog.jwchat.org/2008/12/09/jsjac-v132-released/ coding and stuff Fri, 15 Apr 2011 10:49:25 +0000 hourly 1 http://wordpress.org/?v=3.0.5 Von: alex hu http://blog.jwchat.org/2008/12/09/jsjac-v132-released/#comment-224384 alex hu Sun, 03 Jan 2010 05:29:42 +0000 http://blog.jwchat.org/?p=111#comment-224384 Sir, I need your help! I integrated jwchat into our web application. when the user log in, he/she will be connected to our openfire server automatically through jwchat(I customized it). here is the issue: after the users get connected, I saw bunch of http-bind POST calls every 2-3 seconds from user browsers to our apache server(there is web proxy configured in the apache server to forward requests to our openfire server). Now after we deploy to production. our server crashed. they think this frequent http-bind calls flooded in to apache server and killed our server. I searched the Internet, never see any discussion regarding whether or not this http-bind POST calls will kill the servers. is there any steps I possibly doing wrong? we have at most 2000 concurrent users, is there anyway we can solve it, either by changing our implementation or configuration or upgrade our server hardware architecture. Sir, I need your help!

I integrated jwchat into our web application. when the user log in, he/she will be connected to our openfire server automatically through jwchat(I customized it). here is the issue: after the users get connected, I saw bunch of http-bind POST calls every 2-3 seconds from user browsers to our apache server(there is web proxy configured in the apache server to forward requests to our openfire server). Now after we deploy to production. our server crashed. they think this frequent http-bind calls flooded in to apache server and killed our server.

I searched the Internet, never see any discussion regarding whether or not this http-bind POST calls will kill the servers. is there any steps I possibly doing wrong?

we have at most 2000 concurrent users, is there anyway we can solve it, either by changing our implementation or configuration or upgrade our server hardware architecture.

]]> Von: Steve http://blog.jwchat.org/2008/12/09/jsjac-v132-released/#comment-223464 Steve Tue, 16 Dec 2008 18:25:21 +0000 http://blog.jwchat.org/?p=111#comment-223464 Maty, it's really just minor bug fixed plus what was needed to make jsjac work with firefox 3. If you need to get the full picture have a look at http://trac.jwchat.org/jsjac/changeset?old_path=%2Ftags%2Fjsjac-1.3.1&old=472&new_path=%2Ftags%2Fjsjac-1.3.2&new=494 Maty, it’s really just minor bug fixed plus what was needed to make jsjac work with firefox 3. If you need to get the full picture have a look at

http://trac.jwchat.org/jsjac/changeset?old_path=%2Ftags%2Fjsjac-1.3.1&old=472&new_path=%2Ftags%2Fjsjac-1.3.2&new=494

]]> Von: Maty http://blog.jwchat.org/2008/12/09/jsjac-v132-released/#comment-223449 Maty Tue, 16 Dec 2008 07:15:46 +0000 http://blog.jwchat.org/?p=111#comment-223449 the changelog file in the download zip file has only details on the changes in version 1.3.1. could you please provide some details on the changes between 1.3.1 and 1.3.2 (looking at the trac system, i see only one closed issue for this version)? Thanks, Maty. the changelog file in the download zip file has only details on the changes in version 1.3.1. could you please provide some details on the changes between 1.3.1 and 1.3.2 (looking at the trac system, i see only one closed issue for this version)?
Thanks,
Maty.

]]>