I too could reproduce the issue with current 2.3rc1 (not tried with current trunk).
The problem occurs *only* under Windows, as a very similar configuration under linux (at least with same repositories structure) works fine. Using a debugger I found that command "file.delete();" at line 277 of AbstracFileRepository fails (returns false) *because the XXX.Repository.FileStreamStore file is locked by Windows*, while the XXX.Repository.FileStreamStore file is not and because of that it is successfully deleted. The XXX.Repository.FileStreamStore probably is flushed but not closed when created into the spool, and there may be a difference in behaviour between Windows and Linux. We should investigate further. This is a major bug. Vincenzo Stefano Bagnara wrote: >FWIW I can reproduce the issue with current 2.3rc1 and current trunk. > >Config file as default for 2.3, repositories changed to file in trunk >(we still have derby as default in trunk). > >I connect to remote manager, create an user. Connect to smtp server and >send a message to that user. > >The XXX.Repository.FileStreamStore file is stuck there, in the spool. >If I restart James it got cleaned by the cleaning procedure in >AvalonMailRepository. > >This seems to be a bug. Every file that is spooled remain there until a >restart. This is diskspace leak. > >I tried manually calling from all the places the >ContainerUtil.dispose(mail) and set mail to null to be sure that the >remove were called and I can see that remove is called twice on that >file but it is not removed. It seems that a stream is still opened when >we try to remove it and it's not removed. > >I've not investigated more on this. I only use filerepository in a small >production server that I rarely check. Noel, Vincenzo, can you check >what does it happen in the long term? Maybe this is a test for >Postage... spool folder should increase it size in a linear way if this >bug is there. > >Stefano > >Noel J. Bergman wrote: > > >>Vincenzo Gianferrari Pini wrote: >> >> >> >>>My file based repositories are always clean, and the >>>FileStreamStore files are automatically deleted as >>>soon as sent. >>> >>> >>>It has always been so for me in the last 3 years, >>>in 2.1, 2.2 and now in 2.3. >>> >>> >>I have on very rare occassions seen a stray file. The more common one would >>be a stray .m64 file in temp/. >> >> --- Noel >> >> > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
