[Flow] Occasinal Exception in Production Context

[Dominique Feyer]

Happy co-worker … the cool thing now you know who will pay the beer on friday ;)


--   
ttree sàrl  
Dominique Feyer  
Rue du Valentin 34 et demi
CH - 1004 Lausanne
+41 21  312 36 35  
dfeyer at ttree.ch
ttree.ch - @ttreeagency - plan d’accès

Le 12 août 2014 à 08:56:27, Christian Loock (chl at vkf-renzel.de) a écrit:

I found the source of the problem. It was due to a custom implementation  
if the SimpleFileBackend that a co-worker of mine made, which I wasnt  
aware of. I reset my Cache configs to use the default Cache backends  
again, and now it works fine.


On 11.08.2014 16:25, Christian Loock wrote:
> The same behaviour happens, if I try it on my local machine in  
> production context.
>
> In the ReflectionService, that is an if statement, that checks if the  
> production context is present and wether the cache is frozen.
>
> Is there a way for me to see if a cache is frozen?
>
> On 06.08.2014 13:50, Dominique Feyer wrote:
>> Do you have the same behavior on your local machine when you use the  
>> Production context ?
>>
>> Bests,
>>
>> --  
>> *ttree* sàrl
>> Dominique Feyer
>> Rue du Valentin 34 et demi
>> CH - 1004 Lausanne
>> +41 21 312 36 35
>> dfeyer at ttree.ch
>> ttree.ch <http://www.ttree.ch/> - @ttreeagency  
>> <https://twitter.com/ttreeagency> - plan d’accès  
>> <http://g.co/maps/wwtyz>
>>
>> Le 6 août 2014 à 13:47:44, Christian Loock (chl at vkf-renzel.de  
>> <mailto:chl at vkf-renzel.de>) a écrit:
>>
>>> So...this problem is still there.
>>>
>>> Chace entries inside
>>> Data/Temporary/Production/Cache/Data/Flow_Reflection_RuntimeData are
>>> constantly regenerated. The defaultLifeTime for FileBackend Caches is
>>> set to 0. As far as I understand, this means that caches are never
>>> invalidated until you manually clear the cache. On the other side,
>>> Code/Flow_Object_Classes is not rebuilt automatically. This leads me to
>>> the assumption that there might be wrong with this specific cache
>>> (probably in the settings). However, the Cache Setting Dump does not
>>> really make anything stand out for me. The Problem is, that I don't  
>>> know
>>> where to look (since i can't debug this stuff on the production  
>>> server).
>>>
>>> Can anybody point me to the right place to start?
>>>
>>>
>>> On 30.07.2014 16:21, Christian Loock wrote:
>>> > Here is also one of my Configuration/Caches.yaml and
>>> > Configuration/Production/Caches.yaml:
>>> >
>>> > http://pastebin.com/3XEdW3n3
>>> >
>>> > The only thing that I notices is the defaultLifetime: 0 for the
>>> > Default Cache Backend.
>>> >
>>> >
>>> > On 30.07.2014 16:09, Christian Loock wrote:
>>> >> Here it is:
>>> >>
>>> >> http://pastebin.com/ctDReuGn
>>> >>
>>> >>
>>> >> On 30.07.2014 16:06, Dominique Feyer wrote:
>>> >>> flow configuration:show --type Caches
>>> >>
>>> >
>>>
>>> --  
>>> Christian Loock
>>> Web Developer
>>> Renzel Agentur
>>> www.renzel-agentur.de
>>>
>>> _______________________________________________
>>> Flow mailing list
>>> Flow at lists.typo3.org
>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
>

--  
Christian Loock
Web Developer
Renzel Agentur
www.renzel-agentur.de

_______________________________________________
Flow mailing list
Flow at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/flow