Even Norman is not able to reproduce it.
This could be platform specific: I'm able to reproduce it under windows.

This would also make sense because in unix os you can remove opened
files and they are really removed when the file is closed while under
windows an opened file cannot be deleted.

What OS are you testing?
Stefano

Vincenzo Gianferrari Pini wrote:
> Very strange, this problem *never* occurred to me.
> 
> The only possible difference with your test is that I use file based
> repositories for everything (spool, outgoing, inbox), but db for user
> accounts.
> I will try with the default for 2.3 changing everything to file.
> 
> 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



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to