Skip to main content
Inspiring
August 25, 2015
Question

The service not available message with using Cold Fusion 11

  • August 25, 2015
  • 2 replies
  • 2342 views

Hi,

Below is the information of the Cold Fusion 11 application server:

VM machine
Windows 2008
32 Bit

3 gb of ram
4 CPU's
Cold Fusion 11 Enterprise (all updates installed, except for Update 5)
IIS 7
IIS setting for the application pool Maximum Worker Processes is 1
The number of users in the application range from 500-700.
Only one website on the server
No errors in the IIS or Cold Fusion logs

The following are the settings in the workers.properties:
worker.list=cfusion


worker.cfusion.type=ajp13
worker.cfusion.host=localhost
worker.cfusion.port=8014
worker.cfusion.max_reuse_connections=500
Worker.cfusion.connection_pool_size=800


The following are the settings in the server.xml:
<Connector port="8014" protocol="AJP/1.3" maxThreads= "800" redirectPort="8447" tomcatAuthentication="false" />

At times a message appears when users try to access the login page (The login page does not access the database):
The service not available


From my research the message is coming from IIS and the access to the IIS application pool. In the article
below

URL:
http://www.coldfusionmuse.com/print.cfm?id=76A75909-039F-9E36-866EDF39204E047C

states to increase the value for maxworkerthreads. I cannot find this for Cold Fusion 11.

Also, I have found the Maximum Worker Processes in IIS should be increased.

Has anyone had the issue of the intermittent message of "The service not available"?

Thanks,

Mike

    This topic has been closed for replies.

    2 replies

    Legend
    August 26, 2015

    Hi Mike,

    Something else to consider. Windows and CF 32 bit so Java memory is limited. Perhaps CF Java is having a heap or non heap problem and a minor adjustment needs to be made to heap or non heap to cope better with the type of load.

    Are you familiar with traditional Java logging to a file or using JMX with JDK tools like jconsole? Perhaps there are some errors or warnings in coldfusion-out.log?

    Again, Carl.

    userCold9Author
    Inspiring
    August 26, 2015

    Carl,

    I do not have access to the JMX with JDK tools like jconsole. Also, there are no java error messages in the coldfusion-out.log file.

    In the isapi_redirect.log, I am seeing the following over and over:

    Tue Aug 25 10:14:59.276 2015] [17716:17344] [error] HttpExtensionProc::jk_isapi_plugin.c (2607): service() failed with http error 503

    [Tue Aug 25 10:15:02.224 2015] [17716:17344] [info] jk_open_socket::jk_connect.c (758): connect to 127.0.0.1:8014 failed (errno=61)

    [Tue Aug 25 10:15:02.224 2015] [17716:17344] [info] ajp_connect_to_endpoint::jk_ajp_common.c (1068): Failed opening socket to (127.0.0.1:8014) (errno=61)

    [Tue Aug 25 10:15:02.224 2015] [17716:17344] [error] ajp_send_request::jk_ajp_common.c (1712): (cfusion) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)

    [Tue Aug 25 10:15:02.224 2015] [17716:17344] [info] ajp_service::jk_ajp_common.c (2795): (cfusion) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)

    [Tue Aug 25 10:15:03.332 2015] [17716:17344] [info] jk_open_socket::jk_connect.c (758): connect to 127.0.0.1:8014 failed (errno=61)

    [Tue Aug 25 10:15:03.332 2015] [17716:17344] [info] ajp_connect_to_endpoint::jk_ajp_common.c (1068): Failed opening socket to (127.0.0.1:8014) (errno=61)

    [Tue Aug 25 10:15:03.332 2015] [17716:17344] [error] ajp_send_request::jk_ajp_common.c (1712): (cfusion) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)

    [Tue Aug 25 10:15:03.332 2015] [17716:17344] [info] ajp_service::jk_ajp_common.c (2795): (cfusion) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)

    [Tue Aug 25 10:15:03.332 2015] [17716:17344] [error] ajp_service::jk_ajp_common.c (2815): (cfusion) connecting to tomcat failed.

    Thanks,

    Mike

    Legend
    August 27, 2015

    Hi Mike,

    ISAPI log indicates tomcat connector at IIS can not reach CF. CF-out log is not as useful informing of JVM issues as it used to be in CF9 an earlier. I think an adjustment to JVM will help but some kind of monitoring or logging to know what (heap, non heap or collector) to alter would help.

    Suggest this:
    - set min and max heap to the same and twice default max value to 1024m
    - increase MaxMetaspaceSize to 384m
    - define an initial setting for metaspace -XX:MetaspaceSize=124m

    and more optionally
    - add a setting for code cache -XX:ReservedCodeCacheSize=124m
    - define value for New part of heap -Xmn312m
    - define more threads for the collector -XX:ParallelGCThreads=24

    - control shrink and growth -XX:MinHeapFreeRatio=40 -XX:MaxHeapFreeRatio=70

    Well that is going at it a bit blind without knowing what psrt is having an issue. If it works then good if not then you know what the existing settings are to put them back.

    HTH, Carl.

    Legend
    August 25, 2015

    Hi Mike,

    Your reference to coldfusionmuse post applies to CF9 and earlier which

    used a Jrun webserver connector. CF11 uses tomcat for webserver connector.

    You might like this Adobe blog:

    http://blogs.coldfusion.com/post.cfm/coldfusion-11-iis-connector-tuning

    Many folks find apply a value for "timeout"  in workers.properties and AJP of server.xml is helpful. EG:

    worker.cfusion.connection_pool_timeout = 60 (workers.properties)

    connectionTimeout="60000" (AJP section of server.xml)

    Note server.xml change requires CF restart and workers.properties change requires IIS restart.

    Suggest check tomcat connector log ColdFusion11\config\wsconfig\N\isapi_redirect.log for errors or warnings.

    HTH, Carl.