[
https://issues.apache.org/jira/browse/SHINDIG-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Chabot resolved SHINDIG-973.
----------------------------------
Resolution: Fixed
Fix Version/s: trunk
Thanks for the report & patch, I've added a new 'cache_memcache_pconnect' key
to the config for both the trunk and 1.0.x branch, and if it's set to true it
will use memcache_pconnect, and otherwise connect.
I've used a slightly different config key name to make it consistent with the
other config keys,since they all are 'positive' statements, ie "debug",
"allow_secure_token", "compress_javascript" where 'true' makes it do something
instead of not doing something.
> Memcache pconnect should be optional
> ------------------------------------
>
> Key: SHINDIG-973
> URL: https://issues.apache.org/jira/browse/SHINDIG-973
> Project: Shindig
> Issue Type: Improvement
> Components: PHP
> Affects Versions: 1.0.x-incubating
> Reporter: Nagy Attila
> Fix For: trunk, 1.0.x-incubating
>
> Attachments: shindig_memcache_pconnect_optional.patch
>
>
> Using memcache persistent connections with apache mod_php could result in
> some unexpected behaviour. As I noticed in some installations after memcache
> is restarted, apache begins to segfault until it is restarted too.
> IMHO, in the mpm-prefork environment whether pconnect or connect is more
> powerfull is mostly matter of belief.
> The following patch adds a configuration entry that lets users disable
> pconnects easily.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
