search : worker.properties

select a category, or use search below
(searches all categories and all time range)

displaying top 100 results

Tomcat Load Balancing Sample Worker.Properties File using Status Worker
2609789 CF-3772199 Milan C. Correcting my earlier comment: worker.cfusion.max_reuse_connections=250 will only be added in IIS workers.properties
2608835 CF-3980425 Anit K. Hi John, It seems like a configuration mismatch issue. Can you verify that, the content of workers.properties at \ColdFusion11\config\wsconfig\backup\[Magic Folder].[Backup Folder]\ are similar as workers.properties at \ColdFusion11\config\wsconfig\[Magic Folder]\ ?
6393103 CF-4205636 A. B. In place of: "Result: No PMT settings in worker.properties when you choose not to install or use PMT." please read "Expected Result: No PMT settings in worker.properties when you choose not to install or use PMT."
Comment on Tomcat Load Balancing Sample Worker.Properties File using Status Worker by Anonymous
2608835 CF-3980425 Anit K. Thanks for confirming John. Here is what you need to do, then. Refer to my blog post http://blogs.coldfusion.com/post.cfm/coldfusion-11-iis-connector-tuning. Add the below entry in workers.properties at \ColdFusion11\config\wsconfig\[Magic Folder]\ worker
2608280 CF-4139772 External U. This is a intranet server, we have around 3000 employees. so load is not a problem. I am unable to identify which CFM is causing the Crash, there are no clear information in the logs. Worker.properties dumped below: worker.list=cfusion worker.cfusion.type=ajp13
Comment on Tomcat Load Balancing Sample Worker.Properties File using Status Worker by Anonymous
2609789 CF-3772199 Milan C. ip restriction file should not be created on iis/apache connector installation iiprestrictions_file property should not be added to connector config file in IIS/Apache worker.cfusion.max_reuse_connections=250 should not be added to workers.properties file
Annie Theogaraj Even after installing the ColdFusion2018 update 2, the apache crashes the above mentioned scenario. Hence we had to change the heartbeat_interval=0 in the workers.properties. Could Adobe CF technical team, look into this issue?
2612970 CF-3358792 External U. For update 5 I remembered to back-up my uriworkermap.properties and workers.properties files, but then ColdFusion DELETED THE ENTIRE DIRECTORY, so I lost the back-ups as well. You guys are having a laugh, you really are. Not impressed. -- Adam
2613424 CF-3318699 External U. I was getting this error as well. I went into the server.xml file and added address=127.0.0.1 to the AJP Connector line and it fixed the issue. I was getting the error after turning on ssl. I also changed my workers.properties file to use 127.0.0.1.
2613427 CF-3318104 Adobe D. Made Changes in the following and the server is stable. worker.properties worker.cfusion.connection_pool_size = 500 worker.cfusion.connection_pool_timeout = 60 server.xml maxThreads=500 and connectionTimeout="60000" Followed blog : http
6346370 CF-4205448 Kailash B. Hi,   Can you change the connector port and try again? * Goto your connector magic folder ([CF Home]\config\wsconfig\[Magic folder] * Open workers.properties and change worker.cfusion.port (suppose its 8025 after the change) * Open server.xml ([CF Home
2609789 CF-3772199 Installation/Config : Connector Hank Miller Not supported error when installing Problem Description: In /opt/coldfusion11/config/wsconfig/1/workers.properties file the last line "worker.cfusion.max_reuse_connections=250" is not supported on Solaris 11 Steps to Reproduce: Install
2613515 CF-3300889 External U. I can't replicate the issue at will, but every so often App Pools stop and I get 503s until I restart WWW Pub service. I have updated CF, redid connectors, even tried setting connection Timeout in server.xml and workers.properties to 60 seconds and issues still exist
't reproduce at will. Actual Result: Application Pool Stops Expected Result: Application Pool Doesn't stop Any Workarounds: Attempted manually changing items in workers.properties, server.xml and jvm.config workers.properties Added: worker.cfusion.max_reuse_connections=250 worker
2609661 CF-3811806 External U. Here is the info you requested: 1) This has been observed on Windows Server 2012 Standard. 2) There are 160 sites configured with the "All Sites" option. Most of these sites are not very active. 3) Here are the worker.properties settings for the "All Sites
Configuring Status Worker in Connectors appeared first on ColdFusion. Blog,uri mapping,worker thread,worker.properties
. Is there a walkthrough on how to go about it? I’ve installed CF on the Apache server (Server B) to get the connectors set correctly, and changed the workers.properties file to point to […] The post ColdFusion 2016 Distributed mode Apache web server appeared first on ColdFusion. ColdFusion 2016,Question
}\config\wsconfig\N, where N is the so called magic number (1, 2, 3, ...) corresponding to a ColdFusion instance. 3) Open in a text editor the file worker.properties and examine its contents. Actual Result: The file worker.properties has contents similar to worker.list=myCFInstance1 heartbeat_interval=30 heartbeat
.properties and workers.properties (as detailed here: http://rob.brooks-bilson.com/index.cfm/2012/2/23/Configuring-Multiple-Instances-of-ColdFusion-10-with-Apache-Virtual-Hosts). WSConfig overwrote those changes. THis is not so bad in itself, but it did not back-up the files first so I can remerge your changes and my
:\ColdFusion2018\config\wsconfig\1" folder, and open uriworkermap.properties file and remove the below entry: /connector = cfusion Step 3: Navigate to "C:\ColdFusion2018\config\wsconfig\1" folder and change the heartbeat_interval to 0 in workers.properties. heartbeat_interval=0 Restart both Cold
-to-collect-a-crash-dump-of-an-iis-worker-process-on-iis-7-0-and-above/ https://blogs.msdn.microsoft.com/chaun/2013/11/12/steps-to-catch-a-simple-crash-dump-of-a-crashing-process/ Kindly share the worker.properties file from the connector folder as well: \config\wsconfig\ and the update level of your CF server. You can also get in touch with the CF
as effective as some may hope. And the connector auto-tuning (another option in the PMT) is not perfect, as it only tunes the web server (IIS/Apache) side of the equation (changing dynamically what would be set in the workers.properties file) but NOT the max threads in the server.xml on the CF side
6346370 CF-4205448 A. B. Hi Kailash, We have given the new file a go. Alas, that didn't help either. We also experimented with different values for the connector (in worker.properties and server.xml), and with upgrading using the wsconfig tool. Same issue every time. Nevertheless, we had
folder, for example, C:\ColdFusion2018\config\wsconfig\3. But later: Navigate to the magic folder for cfsite2 (C:\ColdFusion2018\config\wsconfig\2) and open the file worker.properties. Also, the first one reads as if they user SHOULD set it to 3, but of course we have no control of that
but then even scheduler was not helping and on daily basis the Site was going down on peak hours so we uninstalled ColdFusion 10 update 18. Found some of the articles which suggest to tune connectors but even after performing the suggested changes in server.xml and worker.properties file issue still exits
, for changes in the worker properties: worker.cfusion.max_reuse_connections worker.cfusion.connection_pool_size worker.cfusion.connection_pool_timeout and the server.xml maxthreads value on the Connector element. As I have discussed in another feature request I just posted (https
.xml and worker.properties, and and the address field in the server.xml. BTW, there's a problem in the technote in that in the first reference to server.xml there's no reference any sort of secret attribute shown. I can't tell if that was intentional. But then there's also none in the example shown later under
of the ColdFusion Server for the "AppServer Host:" instead of using "localhost" - for example:  192.168.0.123 The resulting workers.properties configuration file that stores the AppServer Host and Port numbers will be copied from the ColdFusion Server to the Distributed Web Server as part of the next
of time tuning the connector settings for our environment. First we tried increasing the "max_reuse_connections" attribute for the connector in its workers.properties file. This would delay the occurrence of the error, but it only provided temporary relief. Then we tried enabling the "connection
:47371424999680] [error] jk_map_validate_property::jk_map.c (404): The attribute 'worker.cfusion .max_reuse_connections' is not supported - please check the documentation for the supported attributes. Modfied {ColdFusion Dir}/config/wsconfig/1/workers.properties to comment out worker