MUC and Derby don't match...
I am sorry to say this. We have found a bug in the MUC component which breaks it for the Derby database. So at the moment MUC component won't work on installations using Derby database. A fix is already ready and will be released later today. I am sorry for all the inconvenience.
35, kobit//tigase.org, 2008-11-13 12:19
The first bug report for the new release...
Just received the first bug report:
#99. If anybody else experienced problems like this please send me the report immediately. Ideally with as much information as possible. Have a look at the comments to this ticket for details what information are useful to me. And also please send me your contact info so I could respond directly.
34, kobit//tigase.org, 2008-11-13 10:31
300 page views in an hour!
New version of the Tigase server has been released. Article published and within an hour the article read counter turned 300 views...
33, kobit//tigase.org, 2008-11-12 22:16
XMPP/Jabber service restarts
We are planing the XMPP server upgare works in coming days to the most recent version. Therefore please be adviced there might be service disruptions in coming days.
32, kobit//tigase.org, 2008-10-03 13:57
Minis from XMPP are back
Due to a significant code rework and changes in many places of the Tigase server short-news were temporarly not working.
This was mainly related to clustering implementation in the Tigase server and need for major code cleanup. The implementation has been finished and slowly all parts of the system are back....
31, kobit//tigase.org, 2008-07-02 10:27
There was a bug in Tigase code which prevented from registering in external transports. It is fixed now so it should be possible to use any transport you like.
Besides... There is also a MSN transport on msn.tigase.org available now.
But as with the tigase.org Jabber service - for testing and experimenting - no guarantee for reliable service.
but in sense of Jabber server application, not a Jabber service for public use. I just don't have resources to offer reliable service for public use.
tigase.org is on my home machine with home ADSL. Even though it is quite reliable I can not guarantee it will always be like this.
Of course I put a lot of effort to make it stable and always on just to show that the application I am working on can offer reliable service.
On the other side I have no objections if you want to setup account on tigase.org and use it as your primary Jabber service.
I can promise you also that I will look at access to remote transports and try to enable them, just to make sure Tigase server can work in such configurarion.
Yes I tried to use the psi client to connect my account on the tigase.org server to the remote jabber.me.uk transport.
I found jabber.org to be very unreliable so I thought I'd setup an account with tigase.org. I figured you are tring to build a reliable server and whenever I have problems I'm sure you need the bug reports ;)
Although I am happy to test tigase.org for you. I'd appreciate it if you could recommend a stable jabber server with support for essentials like offline message retieval and ability to connect to remote transports!
I think the question is about using remote installation of MSN transport not local one.
And actually Tigase site uses Tigase Jabber server... ;-)
Are you running the MSN transport code or did you just add information about it to the jabber.xml file?
You need to download, install, and configure the MSN transport code first - it's a separate download from the core Jabber server.
Ah, ok, thank you I will look at it.
I am not sure if it will work for non-local transports. I will try to do it myself and check in log files why it is not connecting. Maybe there is something in configuration which prevents it from establishing connection.
It's msn.jabber.me.uk but I tried others too.
I mean what is the address of the msn transport you tried to use?
In theory it should work but I have never tried it myself.