PS thats 10,000 1k mails delivered in 690 seconds over 100 simultaneous connections. For what its worth.
> -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] > Sent: 11 October 2002 20:29 > To: James Users List > Subject: RE: James memory leak > > > Cool. Looking forward to it. Also, there are classes that might be good > candidates for object pooling, and we may see some impact from that, too. > > --- Noel > > -----Original Message----- > From: Danny Angus [mailto:[EMAIL PROTECTED]] > Sent: Friday, October 11, 2002 15:05 > To: James Users List > Subject: RE: James memory leak > > > > > I believe THAT particular symptom comes from the > scheduler/watchdog issue, > > which has been documented since Spring. The flood of messages creates a > > huge number of scheduler entries, which persist for several > minutes before > > being released by the scheduler. > > I figured. Whats more I can test your theory.. watch this space. :-) > > > -- > 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]>
