On 30/09/2011 6:27 PM, Holger Hoffstaette wrote:
What I was trying to say is that the bug is much more likely in ZK and one of its racy/buggy codepaths that merely exposes this symptom. They originally hardcoded everything against log4j and therefore probably just didn't see this happen, maybe because log4j is oversynchronized everywhere and thus hiding the root cause.
I don't see how anything a caller of logback, in this case zookeeper, could do to cause the readLock to be unlocked before it is locked. Actually, how could you trigger the observed behavior even if you wanted to trigger it on purpose? Do you have any ideas? -- http://twitter.com/ceki _______________________________________________ logback-dev mailing list [email protected] http://qos.ch/mailman/listinfo/logback-dev
