coldfusion - cflock issue with Fusebox 4 application -
I have received a cf application that currently runs on fusebox 4.
I'm thinking a lot about the time limit of application within the CF Administrator, and I'm not 100% locking and where seaflocks should be used.
& lt; Cflock scope = "application" type = "unique" timeout = "30" & gt; & Lt; Cfinclude template = "fusebox4.runtime.cfmx.cfm" & gt; & Lt; / Cflock & gt; I can now see a CFLL around the main fusebox file. My instinct is telling me that this is not really a good practice. Can someone suggest that this is incorrect for the fusebox app?
I'm sure there is nothing in it Lock Fusebox.runtime.cfmx.cfm Full App You need to check when you lock the entire "application scope" for each request, then you are affecting single-threading for that file. In other words, 2 requests can not run this file at the same time. Since it is a normal file for outline, so it greatly influences your scalability. As the German suggested that an application be used at a discretion - usually once for the application's life.
Meanwhile, there are many things in the specific file (fusebox 4.time.qmmafm) in the question that are not related to the application. You can not run the framework without having to apply it. ... I will remove this lock and check Fusebox 4. To try and determine why anyone felt it necessary to lock the file to start it.
One more thing. There is a "mode" setting in the fusesbox that can be set to DEV or "PROD" (my memory may be bad). It may be that you are set up on DEV - in this situation there are many things that you want to avoid - Mainly each request is to add files again with each request in the "requested" directory. So check one too.
Comments
Post a Comment