1st: forget it. Can you post errors or a way how one may reproduce it? I’‘m not aware of a heavy MUC problem which would have been solved with 2.6.2 so I can’'t recommend an upgrade.
2ndly: patch the open source code or write a plugin for it, it already supports logging.
That said, if you cannot get the MUC service to perform as expected (which is strange for 1.5.x) why don’‘t you run something as a componant (like the MSN gateways). you can turn off MUC internally, and use one of the many different MUC’‘s out there. I won’'t presume to know your setup, but following the directions for whichever one you choose should create an external componant.
Then where and how can I turn off the muc internally? Should I modify in an internal code or just change settings? Please explain to me in detail, im a novice.
But IT, can’'t you just take the name out andsave… that would not show a published muc environment… or is there more to it than that?
NEVERMIND that doesn’'t work! it throws a null value error an then it still shows up. Sorry. I will tell you though that you still should be able to co-locate another muc however
I have a question though, what exactly are you seeing from the internal MUC? You didn;t mention an Error message, and to be honest I have not seen the instability that you are talking about. Can you give us a line from your error logs so we can take a look at it. Barring that, here’’;s some information on what to get to install an external MUC.
Well that would depend on the MUC you are using. Lets say mu-conference, download the package, the jcr-runtime, install the dependancies, then install the packages.
it is for running with Jabberd2, but with the exception of adding it to external componants in Wildfire, everything still should be the same. After you install it and get it to talk with Wildfire, it should show up as one of the external componants. It is a rather lengthy install, but following the instructions should get you where you want to be.
I remember that some bugs that were fixed after 2.5.1 where potentially affecting MUC. I would highly recommend upgrading to the latest release and try again. AFAIK, mu-conference is not being maintained and its implementation is rather old (i.e. not updated to follow JEP changes). Therefore, I would recommend keeping with our MUC implementation and post any errors you see in the log files.