> > > JDBCSpoolRepository has a 60 seconds wait
> > Which should get terminated when notify is called().
> I know how notify() works but james does not call it.
Then we should fix that part.
> the only notify is at the end of store() but there is no notify at
> the unlock()
store() would be called elsewhere in the code to put it into the next
processor, and processor.service() doesn't return until the processor has
finished with the message.
> I don't understand how another thread could contend the message
> before I call spool.unlock().
Personally, I view that code as a mess. As I said, I'd sooner focus on why
we are not getting notify() called when it should, and then eventually
replace the spool manager.
> It seems that when you don't need to move the message to another
repository
> then james doesn't use store().
If you don't call store, you won't persist the change in state, which would
have an impact if the server were restarted.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
