commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17957] - [launcher] - on OutOfMemoryError no message
Date Tue, 17 Jun 2003 03:19:19 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=17957>.
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=17957

[launcher] - on OutOfMemoryError no message





------- Additional Comments From patrickl@apache.org  2003-06-17 03:19 -------
Hmmm. IIRC, I implemented the trapping of java.lang.Errors to handle to case
where  the child process detaches from the parent process i.e. for server and
GUI applications. In these cases, the child's System.out and System.err are not
attached to a terminal (because the parent has exited) and, as a result,
anything printed to either is lost.

I agree that when the child process is run in the foreground i.e. console
applications, your suggestion makes sense. However, I think it would be good to
try keeping the existing functionality for background processes.

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


Mime
View raw message