Thanks a lot, Gato. We will proceed the upgrade to Openfire 3.3.3. One question more: we must change the jabber domain, so we think it's easier to make a new installation and to migrate some tables from wildfire DB to openfire DB, specially  the  jiveroster, changing the jabber domain, of course. Is this approach a good one?

Gato,

About 6 months ago, I have upgraded  the Openfire to release 3.3.3 and changed the jabber domain name. Due to some problems with AD, the number of users has decreased, but now this problem is solved and the original trouble has appeared again: the service runs very well, but the maximum number of connections to the server is 940. After that, a "jabber id or password error" is delivered to any user trying a new connection.

I thought to install the Enterprise plugin, but none of its features suggested to solve this problem. The question is: how can an Openfire server support more than 1000 connections? I'm sure it's possible to achieve  this goal, but maybe there are some commercial constraints. We would like to continue using Openfire, even paying licences. What do we must to do about?

Best regards,

mtstravel,

Are you talking about the "Java Memory" percent bar in the Server Configuration Interface? Is it the "java -Xmx256M" parameter? I do not have much practice in Linux... 

Thanks a lot.

mtstravel,

I'm sure the problem does not come from the AD. So, the java memory is the suspect. From the Openfire configuration interface, the Java Memory  size when the maximum connections number is reached (940) is 70% of 963.00 MB. I have looked for the memory parameters at Openfire launching, but i didn't find any (see attached file). May be the jetty-6.1 uses the default configurations from Linux. The server has Red Hat Enterprise installed and its RAM has 4GB. What the best way? To configure the java memory at the Openfire? To change the memory defaults of Linux? What to you think?

Thanks a lot,

Hi everybody,

I have updated the Openfire version to 3.5.2, then the java memory monitoring has changed. It increases and decreases following the number of connections. It's not linear, but quite reasonable, never higher then 40%. Good, but the problem remains: after 930 connections, the users, including the Console Admin, receive back an "invalid user or password" message. Last week, a new update to 3.6.0: the problem still remains.

Now, it seens that problem is not due to java memory, so let's see the other suspect, the LDAP. I think that AD's parameter MaxPageSize defines the amount of users listed at "Users/Groups" tab, not the amount of connections. There is an open thread about this subject in this forum. None other parameter suggests to be responsable for this (see attached file). When the problem occurs, the Warning Log registers a "PLAIN authentication failure" (see attached file). What exactly does it mean? There is no register about this event in the Error Log. About one hour later, when the users went to lunch, the same user (AdminIM) got a connection, as he does every day.

So, when the amount of connections get close to one thousand, the AD do not authenticate new users due to a "PLAIN authentication failure". Why and what must done to solve this situation?

Thanks a lot for any help,