Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Date: 1 Jun 2004 12:30:19 -0000
Message-ID: <20040601123019.10475.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Cc: 
Subject: 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 max@linuxtag.org  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: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org