On Mar 16, 2006, at 2:43 PM, Mark Womack wrote:
The complete output for this test is below. At first blush, it
appears that the second config file is not parsed correctly, so the
level is never changed to INFO, so the test eventually times out
waiting for the change. Not sure why the file is failing in some
cases. Will probably need to turn up the debugging on
JoranConfigurator.
Likely dying before it ever gets to the JoranConfiguration proper.
The exception reported comes from the underlying XML parser and
indicates that the file either was empty, not completely copied, was
locked or was otherwise unreadable.
[junit] 11:29:02,591 org.apache.log4j.watchdog.FileWatchdog
[DEBUG] - watchdog "test1" reconfiguring from url:
file:/x1/gump/public/workspace/logging-log4j/tests/output/
watchdog.FileWatchdog.test1.xml
The URL used in the test looks flaky, usually file: URL's would start
with 3 slashes. However, looks like it was generated by the proper
calls to the Java libraries, but possibly a mismatch between the
file: URL syntax generated by the JRE and the URL syntax accepted by
the parser might result in the observed exception.
Since the watchdog classes do not appear to be in log4j 1.2, you
should not be under any binary compatibility constraints on the
design. If so, it might be good to refactor the classes, so you do
not have to depend on File -> URL conversion.
p.s. The recent failure with "No Runnable Methods" was due to an bug
in the Ant SVN HEAD where they tried to do something too fancy when
they detected JUnit 4 on the class path. Apparently also hit commons-
collections.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
