Conflict between custom binaryhandler and stale cache

Previous topic

Developer

Next topic

Author	Message
Holger Marx	Friday 29 May 2009 4:39:49 am Since I activate Stale Cache in my eZ Publish installation I run into trouble with my custom binaryhandlers. This is the situation: - eZ Publish 4.1.2 - two of my activated extensions contain one respectively two binaryhandlers - binaryhandlers are activated in override/file.ini.append.php: [BinaryFileSettings] Handler[] Handler[]=extension1aHandler Handler[]=extension2aHandler Handler[]=extension2bHandler Repositories[]=kernel/classes ExtensionRepositories[]=extension1 ExtensionRepositories[]=extension2 - stale cache is activated in override/file.ini.append.php: [ClusteringSettings] FileHandler=eZFS2FileHandler When using the "old" cluster file handler "eZFSFileHandler" the extension binaryhandlers work fine, but now "eZFS2FileHandler" is activated the handlers aren't working anymore! Can somebody tell me if there is a connection/relation between the new cluster file handler and BinaryFileSettings?

Author

Message

Holger Marx

Friday 29 May 2009 4:39:49 am

Since I activate Stale Cache in my eZ Publish installation I run into trouble with my custom binaryhandlers.

This is the situation:

- eZ Publish 4.1.2
- two of my activated extensions contain one respectively two binaryhandlers
- binaryhandlers are activated in override/file.ini.append.php:

[BinaryFileSettings]
Handler[]
Handler[]=extension1aHandler
Handler[]=extension2aHandler
Handler[]=extension2bHandler
Repositories[]=kernel/classes
ExtensionRepositories[]=extension1
ExtensionRepositories[]=extension2

- stale cache is activated in override/file.ini.append.php:

[ClusteringSettings]
FileHandler=eZFS2FileHandler

When using the "old" cluster file handler "eZFSFileHandler" the extension binaryhandlers work fine, but now "eZFS2FileHandler" is activated the handlers aren't working anymore!

Can somebody tell me if there is a connection/relation between the new cluster file handler and BinaryFileSettings?

eZ debug

Timing:	Jan 31 2025 01:21:18
Script start
Timing:	Jan 31 2025 01:21:18
Module start 'layout'
Timing:	Jan 31 2025 01:21:18
Module start 'content'
Timing:	Jan 31 2025 01:21:18
Module end 'content'
Timing:	Jan 31 2025 01:21:18
Script end

Main resources:

Total runtime	0.0223 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0043	588.3594	151.2266
Module start 'layout'	0.0043	0.0041	739.5859	220.7188
Module start 'content'	0.0084	0.0124	960.3047	993.8516
Module end 'content'	0.0209	0.0014	1,954.1563	29.9922
Script end	0.0222		1,984.1484

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	11.2884	14	0.0002
Check MTime	0.0010	4.6621	14	0.0001
Mysql Total
Database connection	0.0006	2.8532	1	0.0006
Mysqli_queries	0.0023	10.5248	3	0.0008
Looping result	0.0000	0.0760	1	0.0000
Template Total	0.0010	4.5	1	0.0010
Template load	0.0008	3.4722	1	0.0008
Template processing	0.0002	0.9982	1	0.0002
Override
Cache load	0.0005	2.2373	1	0.0005
General
dbfile	0.0011	4.7671	8	0.0001
String conversion	0.0000	0.0396	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs