[jira] Commented: (LOG4PHP-71) Using LoggerAppenderFile logging to the log file in one Apache session blocks every other Apache session that tries to write to the file until the original request has been processed

["Christian Grobmeier (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4PHP-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744880#action_12744880 ] 

Christian Grobmeier commented on LOG4PHP-71:
--------------------------------------------

This is indeed not really good. We will check this since i think that the latest code is similar to the version you might use.

Just for the record: are you using apache vers. 2 or 1? Are you running PHP as a module or as CGI? 
Maybe this behaviour is somehow related to the configuration too

> Using LoggerAppenderFile logging to the log file in one Apache session blocks every other Apache session that tries to write to the file until the original request has been processed
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: LOG4PHP-71
>                 URL: https://issues.apache.org/jira/browse/LOG4PHP-71
>             Project: Log4php
>          Issue Type: Bug
>          Components: Code
>         Environment: MAMP, LAMP, WAMP
>            Reporter: Chris Williams
>
> Note: We probably have an older version of log4php than what's currently available.
> We were experiencing problems in our application where one session is waiting on another session. This effectively single threads our Apache requests for different clients. We narrowed this down to our use of log4php.
> The code below will open a file for writing but will not close it until the request has been handled:
> 	$logger = LoggerManager::getLogger('logger');
> 	$logger->debug($message);
> We added the following call and are no longer experiencing the file blocking since it looks like this call closes the file:
> 	LoggerManager::shutdown();
> Is this the expected behavior? Should the log file be kept open between usage?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.