Make jwchat and openFire work

Thanks to this blog post I got it running, though I was not less than five hours hunting. Gee, I wish there was a tool which would let me find the shortcuts to the solution of any problem :-).

After we had followed all the install guides and double and triple checked everything those were the tweaks we needed to do to get it really running:

Edit OpenFire properties - Log into OpenFire as an administrator and add two server properties:
xmpp.httpbind.client.requests.polling = 0
xmpp.httpbind.client.requests.wait = 10
These are required because of a bug where JWChat won’t respect the polling values given to it by the server.

happy chatting away …

15 Comments »

  1. shiva said,

    July 20, 2007 at 4:31 pm

    getting internal server error, it is not connecting to openfire.

  2. Patricia Goldweic said,

    July 26, 2007 at 8:39 pm

    I’ve also been trying to get jwchat to work with Openfire, with no success. I seem to be very close though: I get the chat login screen but with a login button disabled. I’ve followed the original post’s instructions. Did I forget anything?
    BTW, I’m using the jwchat 1.0beta2 released on 7/21/2005. Thanks in advance for any suggestions.

  3. Sellers said,

    September 5, 2007 at 3:33 pm

    I’ve also got the Internal Server Error. I can get that to disappear if I put my server IP DNS name in for [SERVERNAME] all over the config.js file, but it still does not work, the screen comes up 1/2 rendered and the preferences screen only shows the one tab (the other three are grey)

  4. Marcos Abel said,

    September 5, 2007 at 6:10 pm

    I have the same problem of Patricia, when I do all the sutff of the post, the login button is disable.. why is that?

    regards.

  5. milosw said,

    November 22, 2007 at 5:37 pm

    If somebody install JWChat under https, should write whole server URL to the

    httpbase:”https://example.org/http-bind/”

    Maybe somebody find this trick usefull… I spent quite a lot of time for discovering it.

  6. the duder said,

    June 3, 2008 at 5:41 am

    I had that same disabled login button error. I used firefox’s error console (tools->error console) to debug the javascript. I realized that it was referenceing “shared.js” in the jwchat install directory, which didn’t exist. I simply copied it over from shared.js.en and the login button came up

  7. Maestro said,

    July 13, 2008 at 3:10 pm

    After install just run this script in yor install dir. The login button becomes active :)
    find ./ -name “*.en” | awk ‘{print “cp “$0″ “substr($0,0,length($0)-3)}’ | bash

  8. owen said,

    July 30, 2008 at 4:30 pm

    Good news = I got the Login button enabled thanks to the duder’s suggestion (renaming shared.js.en as shared.js).

    Bad news = When I click the Login button I get a 404 (Page Not Found) error.

    I’m struly stuck. Will be checking this page on a daily basis in case anybody has solved it….

  9. owen said,

    July 30, 2008 at 5:16 pm

    Right, I think I\’ve almost got it. It seems all about the files with \".en\" extension; these need to all be renamed, so for example \"search.html.en\" must become \"search.html\" (without the \".en\" part). This applies to *.css.en, *.html.en, and *.js.en

    Now, back up your files before attempting this… Open a DOS prompt, go to your JWChat folder, and type \"rename *.en *.\" (be careful with those dots and asterisks!). You may get a few errors where some of the files already exist without the \".en\" extension; dont worry about those errors. Just refresh your login page and try again.

    Good News = This seemed to initially fix the problem, and I was able to login and it popped up a chat window.
    Bad News = I got a messagebox saying \"service unavailable\".
    Worse News = I now all of a sudden only get a blank page when I login, and cant even right-click on it…

  10. owen said,

    July 30, 2008 at 5:17 pm

    NOTE: please ignore all the backslash characters in that last post, I did not type them, this web page put them in wherever i put a double quote. grrr :o(

  11. owen said,

    July 30, 2008 at 5:22 pm

    UPDATE: It seems to work much nicer in Firefox! My previous test was in IE. In Firefox I can now login and get into the app without any errors.

  12. owen said,

    July 30, 2008 at 6:30 pm

    ….Still can’t actually get any chat working though…!!!

  13. Dinesh Gunarathne said,

    September 12, 2008 at 8:38 am

    hi guys,
    i m trying to configure openfire+jwchat+apache in a windows machine,
    I tried all the things mentioned in several web sites, but i stil couldnt connect to openfire server,
    the error comes “service unavailable”

    __________httpd.conf__________
    AddDefaultCharset UTF-8
    Options +MultiViews

    RewriteEngine On
    RewriteRule http-bind/ http://127.0.0.1:5222/http-bind/

    ___________________________

    ____openfire server settings_________
    * xmpp.httpbind.client.requests.polling = 0
    * xmpp.httpbind.client.requests.wait = 10

    ___config.js file in jwchat folder___________
    * httpbase:”http-bind/”
    * type:”binding”
    * servers_allowed:[SITENAME]

    pls guys tel me how to make it work on above platform?
    thnx

  14. Dinesh Gunarathne said,

    September 12, 2008 at 8:44 am

    Also i cud configure ejabberd with jwchat, we can have group chat,
    its workin fine, but the problem is it uses internal db system.

    i cudnt make it to work on mysql db, eventhough i made settings on “ejabberd.cfg”
    file. db schema also woks fine,

    is there a way? pls,
    thanx!

  15. hire vehicle ins quotes and rates web risk hialeah florida volkswagen passat said,

    June 25, 2009 at 2:37 am

    hire vehicle ins quotes and rates web risk hialeah florida volkswagen passat…

    Bolshevism sky disturb delegate …

RSS feed for comments on this post · TrackBack URL

Leave a Comment