I am failry new to the world of JAMES, so please excuse me if this ends up
being a trivial issue, or if it has already been covered...
I am having a problem getting my JAMES server to process incoming messages
as quickly as I would like them to. I setup a custom Mailet, whose sole
responsibility was to print out the list of recipients for the message, and
then drop it. I noticed that when I put in a random Thread.sleep() staement
in the mailet, that ALL mail processing would stop until the sleep had
finished. I double-checked my config.xml, and I currently have 25 spooler
threads configured. So when I blast 100 messages or so at the server, it
stars processing, then stops while that one thread sleeps (all spool
threads, that is). After the sleep is finished, all of the threads start
handling mail again. Also, I put some debug System.out.println() statements
in my sleep block so that I know it only executes occasionally -- not for
each message.
My assumption would be that while the thread that got flagged for sleeping
was doing that, that other spool threads would still be working. This does
not seem to be the case though. As I mentioned, once the sleep statement
gets hit, no messages are processed until that sleep has finished. Am I
missing some fundamental about how JAMES spool threading works?
Any help would be appreciated.
Thanks,
Brad
