Danny,
That matches my recollection. Can you spot the break? It doesn't work
either on my build from CVS or Peter's, nor do I see from the current code
how it could work without change. I was able to fix it in my build by
modifying James.java to add the IP addresses for each server into the
serverNames collection. However, I'd rather find out why it stopped working
in the first place.
As James is revised, hopefully we can watch for and document (or even
better, FIX) side-effects in the code. I spent much time yesterday
isolating a bug introduced by the spooler changes, where I was seeing very
long (many minutes), non-deterministic, delays in spooling messages from one
processor to another. It turns out that the decision to only call
spool.remove(key) when the message is ghosted broke an undocumented
side-effect that messages were LOCKED by the first worker thread that calls
spool.accept() until the call to spool.remove(). Other threads will check a
locked message, but only the thread that has it locked will work on it.
Removing the call to spool.remove() meant that the message remained locked,
and you'd have to wait for the thread that had it locked to get the message.
Once I understood the problem, it was easy to add an explicit call to
spool.unlock(), and document its importance.
--- Noel
-----Original Message-----
From: Danny Angus [mailto:[EMAIL PROTECTED]]
Sent: Saturday, August 10, 2002 4:26
To: James Developers List
Subject: RE: user@[www.xxx.yyy.zzz]
works ok in 2.0a3, if it doesn't work now it has been broken by new changes.
> -----Original Message-----
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]]
> Sent: 09 August 2002 22:31
> To: James-Dev Mailing List
> Subject: user@[www.xxx.yyy.zzz]
>
>
> I thought that addresses expressed as user@[www.xxx.yyy.zzz] were working
> before, but right now James does NOT appear to be handling them.
> James.isLocalServer(String host) looks up "[www.xxx.yyy.zzz]" and doesn't
> find it.
>
> Am I missing something? Else I'll try to fix this issue.
>
> --- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
