Bill,
James has several places with parallel behavior. The two primary ones
involved in message processing are the spool manager and RemoteDelivery
mailet.
There are multiple spool threads. Each spool thread does process (using a
LinearProcessor) a given message to completion within a particular
processor.
RemoteDelivery defaults to a single thread, but it is easy (I would say
desirable) to add more delivery threads. I believe that this is the
particular configuration item that you want to change. I certainly don't
use just one thread in my production server.
--- Noel
-----Original Message-----
From: bill parducci [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 23:55
To: James Users List
Subject: interesting queueing behavior
whilst watching the gobs of spam fly by on my james server i noticed some
queuing behavior that i found odd. at first i thought that it was just me,
but i have seen some posts ('why is this taking so long to deliver?' kinda
stuff) that indicates that maybe it is something worth asking about.
basically what appears to be happening is that the queues are serviced
serially. in other words, the queue servicer attempts delivery *to
completion* of the first message *before* attempting the second. so if you
have a 'delivery' queue that encounters an error while sending a note (site
doesn't exist, etc.), that servicer will go through the compliment of
time-outs and retries on that note prior to servicing the next one in the
queue; this could take a couple of minutes. i haven't created a reproducible
test (i just have things stable at the moment and would kinda like to keep
it that way :o) but i have noticed this seems to be the case on more than
one occasion.
b
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
