....snip de ja vu...
That's a JavaMail issue, and needs to be eliminated. Regardless of whether
the message is in the DB or a file, we want to stream it if we are
processing it at all. This is orthogonal for having the blob be in a
separate table. The latter allows us improved DB performance (and sharing
of the blob, if that were ever useful).
JavaMail is now open source as part of glassfish
(https://glassfish.dev.java.net/javaee5/mail/).
They "think" they have fixed this problem, but they haven't really as
the solution only works with
the filesystem. If someone is interested I also suggest looking at
removing or fixing the JAF stuff
to avoid synchronizing on the mime handlers or possibly removing JAF
entirely.
-Andy
--
From Windows/Exchange to Linux/Meldware
Buni Meldware Communication Suite
Email, Calendaring, ease of configuration/administration
http://buni.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
