Andrei, No I haven't seen any memory leaks in core James for some time now, but our load profile is different. Also, we don't use RemoteDelivery, we have our own variation.
Steve > -----Original Message----- > From: Andrei Ivanov [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, July 24, 2002 10:16 AM > To: James Users List > Subject: Re: Delivery threads and spool threads > > > Steve, > You might be right I haven check if messages are actually > lost because of that exception since it doesn't happen > frequently. Actually after I dropped thread pool usage for > spool manager (since this doesn't give any benefit) those > exceptions have almost gone (haven't studied why it might > happen yet). Steve, what about memory leaks, have you > experienced this with James? > > Regards, > Andrei > > ----- Original Message ----- > From: "Steve Short" <[EMAIL PROTECTED]> > To: "'James Users List'" <[EMAIL PROTECTED]> > Sent: Wednesday, July 24, 2002 7:36 PM > Subject: RE: Delivery threads and spool threads > > > > Andrei, > > > > Please can you clarify "James spool manager is known to > lose files in > spool > > (file not found exception in log)" ? I've seen the > exceptions, but I > > thought it was a thread synchronization issue, i.e. there's a small > > window wherein the same message can be accept()ed by two threads > > simultaneously. > I > > also thought this was benign because only one of the threads can > > successfully retrieve() the message (which locks it). > > > > Regards > > Steve > > > > > -----Original Message----- > > > From: Andrei Ivanov [mailto:[EMAIL PROTECTED]] > > > Sent: Tuesday, July 23, 2002 11:07 PM > > > To: James Users List > > > Subject: Re: Delivery threads and spool threads > > > > > > > > > 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:james-user-> [EMAIL PROTECTED]> > > > For > > > additional commands, > > > e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For > additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
