ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 25734] - XmlLogger doesn't log when parallel is used.
Date Sat, 13 Oct 2007 02:35:59 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=25734>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=25734





------- Additional Comments From carej@us.ibm.com  2007-10-12 19:35 -------
Every time this topic comes up, I have to remind people that logging in parallel
execution environments is extremely complex & not for the faint of heart.

At IBM we use a custom Antlib to build the WebSphere family of products. One of
the tasks in that antlib handles parallel build dispatch for our many components
based on registered dependencies (of which we have defined our own metadata format).

Strangely enough the most complicated part of getting the parallel dispatch to
work was not the actual dispatch, but rather getting the logs to make any sense.
We found that the standard Ant loggers just aren't up to the task for massively
parallel builds. This is no reflection on Ant: it wasn't designed to handle this
kind of environment.

We ended up writing our own custom logger that uses stacks & thread locals to
present the logging information in a format that is understandable by a human.
you may need to do something similar if you are highly parallel.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message