cluster

Indeed you are right.
Unfortunately I wasn't able to fulfill the promise I made. I was working after normal work hours on the project until a few weeks ago. So the time I could dedicate was very limited thus the progress was sometimes slower than expected.

On top of that I tried to get most demanding features ready first.

The good news is that now I am working on the project full time. That means I can dedicate much more time (all my time) to the project. Of course the highest priority have features requested by people who pay for them but anyway that should speed implementation up significantly. The full-cluster mode is also on the TODO list so I expect it to be ready within a month or 2. Hopefully this time with no more delays.

"Final word regarding cluster mode. I know it is not yet fully functional but this is our primary task at the moment. I think the full cluster mode will be supported by Tigase server within 1 months or so."

Your post was a couple months ago -- how is this progressing, is there a new build coming soon? :-)

Cheers,
Ben

It is a GUI issue. The way they populate the service list. When u add muc.tigase.org as a service spark goes out and discover the service fine however the search result is a list of MUC room they display them in the GUI as services node not as multiuser chat room. so u can't add a room or join because what is listed is an actual room not a service.

Ah, that's good. Thank you for letting me know.
What kind of problem was that?
Could you suggest improvements on our side to avoid problems in the future?

I traced the MUC problem to spark client.
Thanks

1. Tigase supports cluster mode partially only. For now. I am working at the moment on the full cluster mode support. What you can do now is you can deploy client connection managers on several machines so you can distribute the load of the network connections. You can also deploy session manager on several machines but each session manager must serve different domain. So this is basically partial support allowing you distribute the load but does not provide full redundancy.
2. Database replication is a different issue. It is database work and it depends on what database you use. MySQL, Oracle (PostgreSQL??) support full cluster mode. So you can use them in cluster mode as data backend for Tigase server. I have some experience with MySQL in cluster mode so I can offer some advice if you need.
3. I can help you also to setup Tigase on 2 machines. But as I said above you can easily distribute network connections handled by the server. You can easily add more machines to this setup later. But the Session Manager (the central point of the server) will be only one.
4. Regarding the MUC problem. I need a little more before I can help you with this. Is MUC component loaded to the server? Do you use Tigase MUC? Can you browse MUC component with service discovery? Ideally I would like to see your XML configuration file and/or log file.

Final word regarding cluster mode. I know it is not yet fully functional but this is our primary task at the moment. I think the full cluster mode will be supported by Tigase server within 1 months or so.