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
How do you run the server instances?
May I see the xml config file and the parameters you put to application for startup?
And maybe even log file?
You can send it all via email at address 'kobit on tigase.org'
Or you can contact me using Jabber at the same address.
I did already remove the component id under "id-names" of s2s. The funny thing is that the port 5269 is reported 9 times as occupied when starting 10 servers. Any ideas?
The exact log entry is:
2007-05-31 18:03:02 ConnectionOpenThread.addAllWaiting() WARNING: Error: java.net.BindException: Address already in use: bind creating connection for: 5269
BTW I use server 2.8.7. Not too old but still old
Configuration must always be complete so if some settings are missing they are automatically regenerated with default values.
Component is only loaded when 'active' parameter exists and is 'true'.
The best way to disable component is to set 'active' to 'false' or remove it's name from 'id-names' parameter:
<entry type="String[]" key="id-names">
<item value="c2s"/>
<item value="s2s"/>
<item value="sess-man"/>
<item value="ext-comp-1"/>
</entry>
If you remove any component name from the list it won't be loaded next time.
My first approach was to remove all lines above. The funny thing is that the port is still occupied. Is loading the s2s component a default (if s2sactive!=false)?
If you don't need s2s at all then you can disable the component:
Usually the name for the s2s component is 's2s' but it can be different in some installation. But it is quite easy to find it out. Look in your configuration file for following lines:
<entry value="true" type="Boolean" key="s2s.active"/>
<entry value="tigase.server.xmppserver.ServerConnectionManager" type="String" key="s2s.class"/>
The class for s2s will be always the same. This way you can find out what is the name of the component. So to disable the component you have just to set the value for the first item to 'false':
<entry value="false" type="Boolean" key="s2s.active"/>
Alternatively you can change port number for the s2s component:
Look further in the configuration file for a string:
'<component name="s2s">'
Under this section in XML file you will find port numbers used by this component, change them to any value you like....