All,
This patch is manifestly incorrect. Examine the run() method of TimerEventProcessor. It exits immediately, since the while(Thread.currentThread.isInterrupted()) call is false upon start. Run exits, and the thread never actually does anything. Are we done yet? --Peter > -----Original Message----- > From: Harmeet Bedi [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 15, 2002 4:10 AM > To: James Developers List > Subject: Re: [VOTE] Interface for resettable, time-guarded, operations > > Alright folks here is the patch for a scheduler impl. Tested it out. > Applying this on the latest code, and building James will make Danny's > EndToEnd test go on and on. I have tried to run it with 100,00 mail > messages > and 20 workers for a few hours. Before fix it crashed James in a few > minutes. > > If you want to change performance, look at james-config.xml.diff. Change > number of scheduler threads and idle timeout. Haven't tested for > performance > but tweaking these 2 config options should do the trick if that is what > you > want. > > Scheduler reset is a bit heavy and can be made lighter. > > Ok, happy hacking, > later, > Harmeet > > > PS. > here is the Danny's EndToTest diff I made to test this. > > --- EndToEnd.java 14 Oct 2002 16:14:54 -/0000 1.3 > +++ EndToEnd.java 15 Oct 2002 08:08:43 -0000 > @@ -36,7 +36,7 @@ > /** > * The number of worker threads this test invokes > */ > - private int numWorkers = 10; > + private int numWorkers = 20; > > /** > * The size of messages generated by this test case. > > > --- SMTPDeliveryWorker.java 14 Oct 2002 16:14:55 -0000 1.3 > +++ SMTPDeliveryWorker.java 15 Oct 2002 08:09:20 -0000 > @@ -47,7 +47,7 @@ > */ > public void run() { > try { > - for (int run = 0; run < 100; run++) { > + for (int run = 0; run < 10000; run++) { > //move the connect and disconnect out of the loop to > reuse > // the connection for all mail > client.connect("127.0.0.1", 25); -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
