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 25086] - OutOfMemory error leads to confusing error in XmlLogger
Date Sun, 07 Dec 2003 22:32:20 GMT
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=25086>.
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=25086

OutOfMemory error leads to confusing error in XmlLogger





------- Additional Comments From conor@cortexebusiness.com.au  2003-12-07 22:32 -------
In general, when an "out of memory" occurs there is a good chance that things
will be hosed from thereon due to the failure in some operations. This will
apply to far more than the XMLLogger. I would guess that in this case the
XMLLogger has failed to push a context onto the element stack due to the OOM and
this causes the POP failure. 

I think you need to address the root cause of the OOM, rather than try to
address it in the XMLLogger. Is the OOM being reported properly? Is that the issue?

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


Mime
View raw message