i've been observing sporadic exceptions in my fetchmail->sieve->IMAP. the exceptions are thrown even though the mail filtering works fine when the script is run offline. the majority of these exceptions have been fixed by adding read/write locking to the torque mailbox. so, i've been able to focus on the small number left. these don't appear to be IMAP related.
the usual symptom (for these remaining issues) is a failed check in http://svn.apache.org/repos/asf/james/jsieve/trunk/src/main/java/org/apache/jsieve/commands/CommandStateManager.java. i've been wondering recently whether the concurrency isn't quite right in this class. these issues are hard to debug and tend to require a lot of staring at the code. so hopefully, people will help me out by lending an eye ball or two and then stating their opinions. 1 ThreadLocal is created lazily and is used without subclassing. http://java.sun.com/j2se/1.5.0/docs/api/java/lang/ThreadLocal.html recommends subclassing. 2 the instance is set to nulled on a reset. in the case of concurrent threads, a reset in one thread may lead to loss of state in another. a reset on the instance would prevent this. i think that it may better to eliminate the static per-thread singleton manipulation methods and replace them with a ThreadLocal subclass declared final. the reset would then be moved into the instance. opinions? can anyone think of any better approaches? - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
