[
https://issues.apache.org/jira/browse/LOG4PHP-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745058#action_12745058
]
Chris Williams commented on LOG4PHP-71:
---------------------------------------
We're using Apache 2. Using PHP as a module. Tested this by turning off all of
our logging and the app worked as we expected with sessions not blocking each
other. Also, switched back to our old logging architecture and this problem
went away. I'm assuming that the old architecture closes the files after
writing to them.
> 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
> Affects Versions: 2.0
> Environment: MAMP, LAMP, WAMP
> Reporter: Chris Williams
> Fix For: 2.0
>
>
> 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.
