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
I think the log entry you attached here has nothing to do with your problem.
Tigase server allows connections only for selected virtual domains. You can not just start the server and register user accounts in any domain you wish. You have to tell the server for which domains it is supposed to work.
Actually from this log entry I see that you have set it partially correctly. If you look in your XML configuration file you will find entries like this:
<entry type="String[]" key="hostnames"> <item value="localhost"/> <item value="test-domain"/> </entry>I think you added your new domain to c2s component only when you should add it for all components, including sess-man, s2s and bosh if you use it.
Basically you have to add the new domain to all components you want to work or the new domain. This might seem unnecessary complicated at first but this is just a simple installation. In practice you can have more than one sess-man and each of them may work for a different set of domains. The same applies to other components.
This kind of configuration is used if you install Tigase on large deployments and you want to split load on a few machines.
Thanks alot, it works now.
another problem is " I can register user at the same machine using user@localhost, but can not register from another machine using user@domain".
The error message at log file is
"
2008-03-20 09:00:57 SessionManager.processCommand() INFO: Can not find resource connection for packet: to=null, from=null, data=<iq from="c2s@Server1.shineteck.com/192.168.1.7_5222_59.105.134.127_1114" to="sess-man@Server1.shineteck.com" type="set" id="sess1"><command xmlns="http://jabber.org/protocol/commands" node="STREAM_CLOSED"/></iq>, XMLNS=null
"
PS : tigase server is installed behind a NAT server and I have set a virtual host for port 5222
You don't need to do anything special.
You just need to activate s2s component (should be active by default) and you need also valid DNS name for the machine where the Tigase server is installed.
I mean if your Tigase installation works for domain: "your.domain.edu" then the Tigase server installation must be accessible from the internet under this address.