DO NOT REPLY [Bug 28469] - stderr is closed when it is used by jk_logger_file.c
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=28469. 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=28469 stderr is closed when it is used by jk_logger_file.c [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-06-16 14:34 --- OK, patch applied to file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28469] - stderr is closed when it is used by jk_logger_file.c
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=28469. 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=28469 stderr is closed when it is used by jk_logger_file.c --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 09:02 --- Explanation: apr_file_open_stderr does not dup() the system stderr filehandle (fd 2), it just creates a new APR wrapper for fd 2. If you close the APR handle, the original system stderr is closed, and all APR wrappers for fd 2 become invalid. This might be considered an APR bug, because the abstraction offered by APR is not consistent here. I'll attach my solution later today when I'm at my office. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28469] - stderr is closed when it is used by jk_logger_file.c
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=28469. 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=28469 stderr is closed when it is used by jk_logger_file.c --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 12:24 --- Created an attachment (id=11708) workaround patch (untested) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28469] - stderr is closed when it is used by jk_logger_file.c
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=28469. 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=28469 stderr is closed when it is used by jk_logger_file.c --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 12:30 --- I have now attached a patch which works around the problem - it tests whether the previous name was stderr and simply doesn't close stderr handles. I just wrote down that patch without testing... just an idea to start with. Previously, I have commented out the apr_file_close line in jk2_logger_file_init. Object destruction and freeing memory doesn't really work in jk2 anyways (ever tried to run a small JK2 test program with dmalloc or similar heap debuggers? For some classes, there aren't even destructors available.. - email me if you want my help with the code cleanup required here) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28469] - stderr is closed when it is used by jk_logger_file.c
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=28469. 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=28469 stderr is closed when it is used by jk_logger_file.c --- Additional Comments From [EMAIL PROTECTED] 2004-05-28 14:42 --- This is an OK place to put the bug. So we should modify the jk2_workerEnv_init method so that if it already has a handle on stderr, it won't close and reopen? Why doesn't it work actually, after all the second stderr handle should still be valid, no? If you have an actual patch to jk_logger_file.c it'd be welcome. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
