Skip to main content
SamerNafith
SamerNafith
Participant
December 29, 2022
Question

IIS connector log file is too large

  • December 29, 2022
  • 2 replies
  • 790 views

Hi Everyone,

 

IIS connector log (isapi_redirect.log) is around 1.5 GB and keeps increasing, it stores the same warning message each time:

[9544:15528] [warn] ajp_process_callback::jk_ajp_common.c (2245): (cfusion) AJP13 protocol: Reuse is set to false

 

Most important after 2 - 3 days it throws Error 503 Service Unavailable.

 

Server Info:

  • Coldfusion 2018.0.15.330106
  • Java HotSpot(TM) 64-Bit Server VM - 11.0.12+8-LTS-237
  • Tomcat 9.0.60.0
  • IIS 10.0
  • Windows Server 2019

 

Connector Settings:

worker.cfusion.type=ajp13
worker.cfusion.host=localhost
worker.cfusion.port=8018
worker.cfusion.connection_pool_size=1000
worker.cfusion.connection_pool_timeout=60
worker.cfusion.max_reuse_connections=1000

 

Please advice.

Thanks in advance

    This topic has been closed for replies.

    2 replies

    BKBK
    Community Expert
    BKBKCommunity Expert
    Community Expert
    December 30, 2022

    @SamerNafith , First off, it is not your fault. Also, it has nothing to do with your settings or with the way you installed ColdFusion. 

     

    The frequent logging of the warning "Reuse is set to false" in isapi_redirect.log is an old ColdFusion problem. Yes, it is a ColdFusion problem. In fact, you will find references to "Reuse is set to false" in ColdFusion 11 in this forum in 2016.

     

    We've had it for years, on ColdFusion 2016 and ColdFusion 2018. Specifically on instances that run REST.

     

    It was especially rampant in 2020 in ColdFusion 2018. The message was then logged every second, with log files exceeding 1.5 GB.

     

    I did look into it. My conclusion is that the "Reuse is set to false" warning is the result of a change in behaviour in the ColdFusion-Tomcat interaction. Very likely a change in the period 2018-2020, when ColdFusion began logging the warning every second..

     

    I once contacted the Adobe ColdFusion Team about the issue. Following their suggestions, I experimented by changing some of the connector, server.xml and context.xml settings. Alas, none of the changes helped. In addition I opened a ticket in the Tomcat forum. No dice either.

     

    Our eventual solution:

    • Stop ColdFusion (at a convenient time, for example, during routine maintenance);
    • Copy the massive isapi_redirect.log to an archive, and delete the file from the ColdFusion server. When you next restart ColdFusion, a new isapi_redirect.log file will automatically be created.

     

     I hope the ColdFusion Team continues to look for a solution. 

     

     

    SamerNafith
    SamerNafithAuthor
    Participant
    January 3, 2023

    Thank you @BKBK for your input, I will try to do this regularly until we have a fix for this.

    The major issue now, it throws Error 503 every two days

     

    [Tue Jan 03 12:25:57.002 2023] [24204:23192] [info] ajp_connect_to_endpoint::jk_ajp_common.c (1140): (cfusion) Failed opening socket to (127.0.0.1:8018) (errno=48)
    [Tue Jan 03 12:25:57.005 2023] [24204:23192] [error] ajp_send_request::jk_ajp_common.c (1811): (cfusion) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=48)
    [Tue Jan 03 12:25:57.007 2023] [24204:23192] [info] ajp_service::jk_ajp_common.c (2982): (cfusion) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)

    BKBK
    Community Expert
    BKBKCommunity Expert
    Community Expert
    January 3, 2023

    Hi @SamerNafith ,

    The 503 error is probably not related to the size of isapi_redirect.log. In all likelihood, the 503 has to do with the following connector settings:

     

    1. secret
    2. address

     

    (1) In workers.properties, specify the secret property. This can be any string you choose. But use a UUID, for example, a UUID generated by means of the ColdFusion function createUUID().

     

    worker.cfusion.secret=b242832c-0d0c-a3b8-8b34edef24bfb1fd

     

    (2) In \cfusion\runtime\conf\server.xml, add an attribute called secret to the connector XML element. Make sure it has the same value as the secret in workers.properties.

    Also add an attribute called address, giving it the value "::1".

     

    <!-- AJP connector -->
<Connector port="8018" connectionTimeout="60000" redirectPort="8453" protocol="AJP/1.3" tomcatAuthentication="false" maxThreads="1000" address="::1" secret="b242832c-0d0c-a3b8-8b34edef24bfb1fd"/>

     

    Save the changes and restart ColdFusion.

    Priyank Shrivastava.
    Community Manager
    Priyank Shrivastava.Community Manager
    Community Manager
    December 29, 2022

    Hi @SamerNafith 

     

    Please check the Connector Log_Level and see if it is set to Debug.

    Go to \ColdFusin2018\config\wsconfig\{magic_number}

    Take the backup of isapi_redirect.properties and then open the file. 

    There is an entry named - log_level= info/debug  - If it is set to debug, please change it to "info"

    Restart IIS.  In case, it doesn't let you save the file, then stop IIS before making any changes. 

    Please let me know if that helps.

     

    Thanks,Priyank Shrivastava
    SamerNafith
    SamerNafithAuthor
    Participant
    December 29, 2022

    Thank you @Priyank Shrivastava.  for your response.

    I have checked the file and the value is info

     

    File content:

    extension_uri= /jakarta/isapi_redirect.dll
    log_file= C:\ColdFusion2018\config\wsconfig\1\isapi_redirect.log
    log_level= info
    worker_file= C:\ColdFusion2018\config\wsconfig\1\workers.properties
    worker_mount_file= C:\ColdFusion2018\config\wsconfig\1\uriworkermap.properties
    iis_buffer_enable= true
    auth_complete= 1
    iis_skip_custom_errors_enable= false

     

    Priyank Shrivastava.
    Community Manager
    Priyank Shrivastava.Community Manager
    Community Manager
    December 29, 2022

    Thanks, may I now how is the traffic in your website or how many website you are running with single connector?

     

    It may be a possibility that the number of reuse connections are getting exhausted and that's when it will start throwing 503 error.

     

    Thanks,Priyank Shrivastava
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices