I'm pretty sure the connection isn't used (or held open) until the
writeMessageTo() is called. You're implying that if you have 20 messages in
your (JDBC managed) inbox, you have 20 open db connections. I'm almost
positive this isn't the case, and if it is, it clearly needs to be fixed.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
----- Original Message -----
From: "Oki DZ" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 06, 2001 2:49 AM
Subject: Re: Scalability
> On Wed, 5 Sep 2001, Serge Knystautas wrote:
>
> > I think I've heard a few hundred, but not thousands. I would definitely
> > wait for the code in CVS to be released, because the current 1.2.1
release
> > is parsing messages during pop retrieval, which will dramatically slow
> > retrieval.
>
> It needs some improvement, I think; ie: regarding how the list of the
> messages is maintained by POP3Handler. Currently, the list, ie:
> userMailbox, holds MailImpl objects. Would not be a problem in
> repositories other than JDBC. But if the mail repository is in a database,
> you'd have a list of retrieved messages. The actual contents wouldn't
> really be retrieved until MailImpl.writeMessageTo(), but still, there
> would be many database connections open (by MimeMessageJDBCSource). If you
> use db connection pooling, that would eat up resources quite a lot; as
> long as the message list (userMailbox) has some elements in it, then that
> numbers of connections would be open also.
>
> Oki
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
