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 32566] - OutOfMemory if filesize are greater than 7 MB
Date Thu, 09 Dec 2004 22:05:45 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=32566>.
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=32566





------- Additional Comments From ant@kruithof.xs4all.nl  2004-12-09 23:05 -------
Hi,

Typically ant tasks are not thread safe. See also
http://wiki.apache.org/ant/AntWeaknessesAndProblems

In particular a single instance of a task need not be thread safe as a task is
executed in a single thread (unless the task itself spawns threads).

The thread that created the task at parse time (and hence also used all the
setters on the task) may be another one than the thread executing the task in
case the parallel task is used, these other threads however are guaranteed to be
created after the parsing and creation of tasks has taken place (e.g. no
synchronized to aquire a lock / to make sure all data is re-read is needed on
the new thread, a new thread will always initially read the data from main
memory) it may be necessary though to previously release a lock to make sure all
data from the created tasks and properties upto the point where the parallel
task is started are available in main memory though.


-- 
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