Custom Query (267 matches)

PHP 5.4.3 Apache 2.2.22 64bit. Win 2008 64bit xcache 2.0.1

We have several instance of the Drupal CMS installed on our server which means several copies of the same files and file structure, just in different base directories. We do this so we can break a development version and not affect live, however, they run through one Apache instance and therefore one PHP and xcache instance.

It appears that when xcache is enabled we get frequent but intermittent and apparently fairly random "cannot redeclare class" errors in the PHP error log. These are fatal errors so the page completely fails when this happens. Disabling xcache completely eliminates the problem.

Since these errors are usually caused by either loading the same file twice (include instead of include_once) or by loading two files which have the same class declared in them I wonder if xcache is not using the entire filepath to identify cached files? After all, we have several instances of the same file, each of which has the same size etc.

Evidence for this comes from the error stack which shows the source of the error itself from instance A where all the other entries in the stack are in instance B. This should never happen and as stated, when xcache is disabled, it doesn't.

Administrator Web Scripts monitoring/managing the cache has to be provided in XCache.

good news: it's already done, yet need sometime to be published.

An opcode cacher makes php faster, but stablability is far more important than performance.

Have a scheme to disable xcache if the cache is corrupted would be nice.

• on SIGSEGV, mark the xcache_corrupted as true, skip using cache. the flag "xcache_corrupted" has to be in cache too...
• have a cron script to restart php if it find a core dump.