[Server-devel] testing ejabberd
Douglas Bagnall
douglas at paradise.net.nz
Wed Sep 24 00:29:26 EDT 2008
Guillaume,
> Would be helpful if you could upload Gabble log somewhere. Before
> starting hyperactivity, launch Gabble manually like this:
> GABBLE_PERSIST=1 GABBLE_LOGFILE=/tmp/gabble.log GABBLE_DEBUG=all
> LM_DEBUG=net /usr/lib/telepathy/telepathy-gabble
Thanks. That was enough for me to sort it out -- the problem was
caused by ejabberd restricting the number of registrations per IP
address. Adding "{registration_timeout, infinity}." to ejabberd.cfg
fixed it.
I've put the log at http://halo.gen.nz/gabble-wired-connection-1.log
but only in case you are curious.
I've tested up to about 350 users from various machines at various
activity rates. Collaboration continues to work while ejabberd is
under this load, while its memory use grows to around 160MB. I'll
report on this in more detail soon.
Douglas
More information about the Server-devel
mailing list