My apologies for the delayed response. It's been one fire after
another lately :)
kevin_d_cl...@comcast.net (Kevin D. Clark) writes:
> 1: It sounds like you're experiencing a memory leak in
>your Openfire server.
It was indeed a memory leak, exacerbated by one particular client.
We're at
On Fri, Jan 8, 2010 at 2:29 PM, Kevin D. Clark
wrote:
> The way that I try to design protocols and systems is to assume that
> the entity at other end of the connection might be some infinitely bad
> thing that is looking to take down the system.
Indeed. That's a hallmark of good design. Any
Ben Scott writes:
> While still true, there are cases where it's less cut-and-dry: In
> other protocols, I've seen clients do the equivalent of "repeated
> malloc without free". Of course, the server should place limits on
> resources a client can allocate, but some people consider that kind o
On Fri, Jan 8, 2010 at 10:53 AM, Kevin D. Clark
wrote:
> 4: If some particular client exacerbates this problem, this
> is interesting, but the root cause is still that the
> server is buggy.
While still true, there are cases where it's less cut-and-dry: In
other protocols, I've seen clie
Paul Lussier writes:
> Openfire docs don't seem to have a lot of information on performance
> tuning, does anyone here have any experience with tuning this thing for
> use in large environments with lots of users ?
I don't have too many helpful things to say here except:
1: It sounds like you'r
Ed Robbins writes:
> From a Java perspective, have you utilized any of the JMX tools to
> connect to it while it's running to view it's vitals? You can also
> force it to dump it's heap and then analyze it to see what's using all
> of the memory, that may be helpful in determining what the culpr
Ben Eisenbraun wrote:
> Hey Paul,
>
>
>> Is anyone here using the Openfire Jabber server with large numbers of
>> users?
>>
>
> Nope. There are only about 8 of us, but..
>
>
>> However, we are finding that it needs to be whacked fairly f
Hey Paul,
> Is anyone here using the Openfire Jabber server with large numbers of
> users?
Nope. There are only about 8 of us, but..
> However, we are finding that it needs to be whacked fairly frequently.
> We've seen Java OOM errors, etc.
We started getting these a few
Hi all,
Is anyone here using the Openfire Jabber server with large numbers of
users?
I have a server running Debian 4 with 2GB RAM on a Dell PowerEdge 850
with 2 cores. This is a fairly decent machine, and ought to be more
than enough power for running a Jabber server.
However, we are finding
