Shilpa,
You've got me convinced.
Having read the thread, more James code and the relevant portions of
Cornerstone, I believe that you are actually underestimating. If what
appears to be the case from my reading of the code, and what you and Peter
Donald say is happening, then you are underestimating the potential
magnitude of the problem by orders. Trace through the doDATA method. It
appears to be that SchedulerNotifyInputStream resets the trigger for EVERY
BYTE OF DATA in the message stream; SchedulerNotifyOutputStream does the
same when writing. If those are really resulting in a new queue entry for
each byte of data (which is what appears to be the case), that's brutal, and
really needs to be addressed either in Avalon or in James.
As far as I can see, James is using this as a watchdog timer, which does not
appear to be the design point for Avalon's facility, based upon their own
comments, design and implementation. And even the workaround to Avalon of
adding another thread or doing the replacement during the reset would be
performance prohibitive given that the trigger is reset for each byte of
data read from the stream. I've done a grep of James to find all uses of
the trigger code, and it looks to be similar in all cases. Perhaps a more
efficient watchdog solution can be devised, maybe tied to the handler
instance. I'd sooner create a watchdog thread per handler than have 100s of
thousands (or millions) of events in the scheduler queue.
Am I reading this correctly? Your throughts?
--- Noel
-----Original Message-----
From: Shilpa Dalmia [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 21, 2002 19:26
To: '[EMAIL PROTECTED]'
Subject: FW: SMTPHandler connection timeout
You can look at the foll. avalon mailing list thread on this issue where
they have given an explanation for this.
http://www.mail-archive.com/[email protected]/msg08660.html
I have a implemented a temporary solution for this issue, which fixes the
problem.
Shilpa
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
