DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24928>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24928

Multithreaded JUnit test cases with Log4J and ANT

           Summary: Multithreaded JUnit test cases with Log4J and ANT
           Product: Ant
           Version: 1.5.4
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Optional Tasks
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Using JUnit, I have created an ActiveTestSuite in which n threads will execute 
a set of tests m times.  All classes which are involved in my testsuite are 
using the root logger (Log4J).  The root logger is configured to log all 
messages to the console.  The reason why I am writing to the console is so the 
JUnit task can intercept and write the logs to the XML file that it generates.

The symptom I am experiencing is that my main thread writes to the console 
which the JUnit ANT task captures (i.e. the text is non-visible during 
testsuite execution through ANT), but all my spawned threads continue to write 
to the console even though the same Logger is being used.  When I looked in 
the generated JUnit XML documents, only the logs for the main thread are 
present.

As a test, I inserted a System.out in one of the methods a test thread 
executes.  Again, the message is only displayed to the console and is not 
captured by the JUnit task.

I apologize if this "issue" has already been recorded and I'm sorry that I 
currently have no further details at the present (i.e. a solution for 
instance).  Does anyone have any suggestions?

Cheers!

-- Ross

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to