I assume this is with the latest snapshot... there is a bug (in James) where messages moving from one repository to the next are not "waking" the thread that monitors that new repository.
I'm pretty sure I know which jump it is, but it doesn't make a lot of sense why that jump is having trouble. Basically, it goes from SMTP handler -> mainspool. the spool handler immediately picks it up and puts it into the transport repository. this is where it sits for 1-2 minutes because the spool handler doesn't realize the transport repository has a message to process. Finally, a minute or so passes (the waiting timeout), it checks again, and moves that to the inbox. Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/ ----- Original Message ----- From: "Blezek, Daniel J (CRD)" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 24, 2002 11:06 AM Subject: James speed > Hi all, > > I've been using James to test a small java program that needs to send/fetch/process email from a > SMTP POP3 server combination(I run on MacOSX Java 1.2). When I send an email message through James > SMTP, it often takes 1-2 minutes to be processed and available for POP3 fetching. I could not find > any options in the configuration file to speed this up, and setting the number of spool threads > higher didn't seem to help. Watching the CPU meter shows almost no activity. > > Some possibilites came to mind: > > I am not connected to the network, so James might be waiting for DNS timeouts, but I tried to > configur e things so it would not do any DNS lookups > > I missed a configuration parameter for some sort of delay > > Dare I say it? a bug in Apple's implementation of Java? > > Any suggestions? > -dan > > -- > Daniel Blezek, Ph.D. > [EMAIL PROTECTED] > Visualization and Computer Vision Lab, Imaging Technologies > GE Corporate Research & Development -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
