From: <anj...@t-...> - 2003-06-30 22:51:27
|
Hi Nick, Am Montag, 30.06.03 um 23:59 Uhr schrieb Nick Pilch: > If I turn on debugging for all groups and set the debug level to 2, > occasionally I get messages from EOF like "***EODatabaseContext: > access without lock!". This message is followed by a stack trace. > > The first message is intercepted by the wonder logging system, but the > stack trace is not! If WOOutputPath is set, this stack trace ends up > in the log file specified in WOOutputPath. > > Thought you might like to know. This complicates debugging. Hm, strange. Don't know what to make of it, though? > I had a thought that Wonder could examine the value of WOOutputPath > and create a log4j appender to write to the file specified. However, > WO is doing things behind the scenes with the value of WOOutputPath, > so perhaps it wouldn't work. > > BTW, the "access without lock" messages appear to be a bug in WO since > I am certain that I have locked down my EOEditingContexts before I use > them, and the stack traces show that they are deep within some WO code > that is processing a message from a Java Client. Yes. AFAIK, this is a confirmed bug. Cheers, Anjo |