On Tue, 19 Jun 2007 17:46:24 +1200, "Mark Derricutt" <[EMAIL PROTECTED]> wrote: > Hey all, > > Have an odd problem I was hoping someone could give me some ideas on > how/where I could look to diagnose the problem. > > Our application uses james 2.2.0 (not sure of the point release off hand) > to > pass messages to our application via a mailet. Sometimes we're noticing > an > occasional message gets left behind in the spool directory after being > processed. > > There doesn't seem to be any exception or error messages in the logs for > the > message id or sender etc. that I can see, just the two files > (FileStreamStore and FileObjectStore) for each message that somehow gets > left behind. > > Its as thou James failed to physically delete the files, but thinks that > it > has. Does anyone know if this was a known bug in James 2.2.0 at all? > > Cheers, > Mark >
Hi Mark, there were some porblems with files which were not probaly delete in james 2.2.0 . This was fixed in james 2.3.0. Anyway you should upgrade to james 2.3.1 as soon as possible. bye Norman --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
