Just a follow on note.
We were never able to get over 595 sessions. Memory errors would start at around 550 users. In addition, the server would just deteriorate over time and eventually throw errors on the SQL threads and others - TCP/IP resources all used up, etc. We had to re-start the service every 3 days.
The impact on the user community was immense, and we were directed to ‘‘pull the plug’’ on the new server and roll back to our jabbber 1.4 environment. It’'s a shame. I really like the wildfire implementation - the tools, ease of use, plug-ins, etc.
The worst part is that we’‘ve managed to sour management on Jabber as a corporate IM standard now. I don’'t haven any support to ''get it working and try again. Instead they want to focus on Micro$oft…
The bottom line is that the addition of external LDAP/AD authentication just overwhelmed Wildfire, and we had not anticipated that when choosing and testing the server. I sure wish I had done a lab-based load test of 2000 users before migrating…
Pat