Hello, good people. I've configured ejabberd, apache, tomcat5, and muckl/jwchat in what *looks* like the correct configuration. ejabberd works with muc and sasl anonymous in other clients and gives me the JabberHTTPBind webapp via mod_jk. Loading when I access MUCkl, however, i get an internal server error. Nothing happens in the ejabberd logs and so I'm sure that the JabberHTTPBind servlet is not actually 'bound' to ejabberd. In fact, in doing the configuration, I can't see where that is supposed to happen.
This is the tutorial I followed:
In there it's unclear how exactly tomcat/jabberhttbind talks to ejabberd.
Any clues how this is done? Is punjab a better solution? Looking over it's docs, I wasn't sure it would be any more clear than jabberhttpbind's.
Perhaps the ejabberd config needs some editing to get this done?
Thanks so much,
gm
getting further
I see that jabberhttpbind can bind to an arbitrary jabber server, so that helps me understand it a bit. I do have errors in the mod_jk log, so my configuration must have a problem:
[Wed Nov 01 20:54:09 2006] [info] ajp_send_request::jk_ajp_common.c (1178): Socket 16 is not connected any more (errno=-1)
[Wed Nov 01 20:54:09 2006] [info] ajp_send_request::jk_ajp_common.c (1202): Error sending request. Will try another pooled connection
[Wed Nov 01 20:54:09 2006] [info] ajp_send_request::jk_ajp_common.c (1225): All endpoints are disconnected or dead
[Wed Nov 01 20:54:09 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1
Anyway, once this works I'll put up a tutorial for linux+ejabberd+[web client]. Any with a working installation who can provide their tomcat config would be hero. ;p
gm