james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Ivanov" <my...@surfeu.fi>
Subject sources Re: James SMTPServer load test - from 6req/s and crash -> 26req/s no crash
Date Mon, 03 Jun 2002 16:59:08 GMT
Hi, Serge
here are the sources of modified / new James classes. To test it just unzip
and copy over existing src (***DO not do it for you configured (development)
James since it will overwrite james-config.xml!!!). When build and run.

All other James's servers can be changed same way (so they will inherit from
core.AbstractServer). No need to use AbstractService any more...

Andrei
PS in fact it will (almost :-) you will see the difference immideately) work
just fine with original james-config.xml. I've included this file just to
illustrate new options for configuring smtpserver.

----- Original Message -----
From: "Serge Knystautas" <sergek@lokitech.com>
To: "James Developers List" <james-dev@jakarta.apache.org>
Sent: Monday, June 03, 2002 8:45 AM
Subject: Re: James SMTPServer load test - from 6req/s and crash -> 26req/s
no crash


> Andrei,
>
> Please send any/all patches to the listserv.  One of us will try to
> review and commit them assuming we don't see any problems.  Your
> improvements sound very encouraging.
> --
> Serge Knystautas
> Loki Technologies - Unstoppable Websites
> http://www.lokitech.com/
>
> Andrei Ivanov wrote:
> > Hi,
> > Please refer to my previous post about James SMTPServer load test for
more
> > details on this issue.
> > In short:
> > 1. James SMTPServer part was tested for number of incoming 4KB mails it
can
> > accept
> > 2. All other parts of James were not in use by commenting out
> > mailServer.sendMail(mail); @line 615 in SMTPHandler.
> > 3. James SMTPServer crashed after certain number of requests with
> > OutOfMemory exception
> >
> > Studying the results of my previous tests showed most likely the problem
is
> > in how SMTPHandler unallocates resources when connection has to be
released.
> > In fact it didn't do any resources release. So I put my efforts in
> > refactoring
> > SMTPServer
> > SMTPHandler (only few changes)
> > BaseConnectionHandler
> >
> > I replaced BaseConnectioHandler with AbstractServer which implements
> > ConnectionHandlerFactory.
> > Every other server class can now inherit from new AbstractServer  by
> > implementing its "public abstract createConnectionHandler()".
> > Main achievement is that this way it is possible to unallocate
explicitly
> > resources used by any connection handler.
> > So I made SMTPHandler to be disposable and simply "multiplied by null"
all
> > its resources in its dispose.
> >
> > The result is in subject of this letter.
> > Opinions, ideas?
> >
> > Andrei
> >
> > PS still using java 1.3.1_02 :-)
>
>
> --
> To unsubscribe, e-mail:
<mailto:james-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:james-dev-help@jakarta.apache.org>
>

Mime
View raw message