Everything appears fine on the nascent test system I set up (above)....so out of curiosity I logged in to our production server using Empathy 188.8.131.52 from an Ubuntu 9.10 virtual machine. And bingo - it's all on. Empathy indeed appears to be the kiss of death for OpenFire.
I can confirm that what I'm seeing is without the monitoring plugin installed.
The production system details:
Version: Openfire 3.6.4
Java Version: 1.6.0_07 Sun Microsystems Inc. -- Java HotSpot(TM) Server VM
OS / Hardware: Linux / i386
Java Memory 171.62 MB of 253.19 MB (67.8%) used
Other differences from the above system I posted:
I haven't got JConsole hooked up so am monitoring by refreshing the OF admin console page
Over the course of an hour I have observed JVM memory usage creep from 20 percent with half a dozen logged on users to at the time of writing 80 percent consumed.
All other users are on Spark 2.5.8 or Pidgin. I am the only user with Empathy.
The only plug-ins installed on this system are:
We are not using Red5 Sparkweb functionality - i.e we have it set on a trial basis for users if they wish to tinker, but as yet no-one is actually using it.
Another observation - if you really want to exacerbate the behaviour, quit Empathy and fire it back up in rapid sucession...
I'm not going to be able to get you thread dumps with this particular setup (sorry), but will return to my test system tomorrow and try and get some concrete data for you.
EDIT: JVM heap size just hit 90 percent of capacity...so I'm gonna do a quick bounce of the server before anyone notices...
Message was edited by: davenz