Hello, I haven't tested james with more than 50 threads but I might have some experience which can be useful (I used continuous loads with short size messages (about 4-10KB) during days with rate about 6 messages per second). The main problem I cam across is the memory leak. It was consuming about 200bytes per message (on W2K). This consumption doesn't start immediately but became obvious after first 100 000 messages and remains constant afterwards. Have you checked if your James leaks memory during blasts? Secondly, James spool manager is known to lose files in spool (file not found exception in log). Did you observe those exceptions in logs? Have you checked that?
> It seems the delivery threads are optimized What do you mean by this? Andrei ----- Original Message ----- From: "Ramon Gonzalez" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 24, 2002 3:58 AM Subject: Delivery threads and spool threads > Hello, > > I am currently using JAMES at work to deliver approximately 17,000 email > messages per "blast" to the trade industry I serve. After every "blast" I -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
