james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Serge Knystautas" <ser...@lokitech.com>
Subject Re: Sticking with one undeliverable message
Date Fri, 08 Mar 2002 16:40:19 GMT
If I were a gambling man, I would say b) is the culprit.  I'm pretty sure
System.err will spew to the console, and c) is easy enough to check by
sticking some debug in initialization or earlier in the code.

Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com/
----- Original Message -----
From: "Gordon Ross" <G.Ross@ccw.gov.uk>
To: <james-dev@jakarta.apache.org>
Sent: Friday, March 08, 2002 10:34 AM
Subject: Re: Sticking with one undeliverable message


> Nope, still no joy.
>
> Just to clarify, I've placed a couple of System.err.printlns in the
> deliver method in the RemoteDelivery.java.
>
> Either:
>
> a) My logging statements don't work...
> b) I'm building & re-installing James wrong,
> c) the deliver method isn't getting called and I should be looking
> elsewhere....
>
> GTG


--
To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>


Mime
View raw message