Alexander Kunkel wrote:
Hi Stefano,
I remember 60seconds and not 120 but maybe you have 2
spooling
60 seconds are correct. I checked it with a watch.
I hope I fixed this issue in the current trunk so 2.3.0 should not
suffer this problem.
How i can test it?
I use james-binary-2.3-dev.zip downloaded yesterday containing files
from yesterday.
Alexander
I ran a few tests and found a deadlock issue.
I just removed a synchronization in a wrapper and this should solve
(again?!) the problem described.
Please let me know if it works with the next build!
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
