August 23, 2021
connection error when updating to CF 2018 v11
Comments
(5)
August 23, 2021
connection error when updating to CF 2018 v11
Newbie 1 posts
Followers: 0 people
(5)

I have CF 2018 Enterprise, and was trying to update from v4 to v11. I have IIS running on a web server (different machine) and CF running on another machine (app server). v4 everything works as it should, but when I upgrade to v11, I see the following errors in isapi_redirect.txt file (I run wsconfig.ext on the webserver to establish the connection between the web server (IIS) and app server (CF). Here are the errors I am seeing in the isapi_redirect.txt

[Sat Aug 21 10:55:10.690 2021] [5916:5976] [info] jk_open_socket::jk_connect.c (816): connect to [CF App server IP address]:8018 failed (errno=61)
[Sat Aug 21 10:55:10.690 2021] [5916:5976] [info] ajp_connect_to_endpoint::jk_ajp_common.c (1140): (cfusion) Failed opening socket to ([CF App server IP address]:8018) (errno=61)
[Sat Aug 21 10:55:10.690 2021] [5916:5976] [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=61)
[Sat Aug 21 10:55:10.690 2021] [5916:5976] [info] ajp_service::jk_ajp_common.c (2982): (cfusion) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)
[Sat Aug 21 10:55:11.830 2021] [5916:5976] [info] jk_open_socket::jk_connect.c (816): connect to [CF App server IP address]:8018 failed (errno=61)
[Sat Aug 21 10:55:11.830 2021] [5916:5976] [info] ajp_connect_to_endpoint::jk_ajp_common.c (1140): (cfusion) Failed opening socket to ([CF App server IP address]:8018) (errno=61)
[Sat Aug 21 10:55:11.830 2021] [5916:5976] [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=61)
[Sat Aug 21 10:55:11.830 2021] [5916:5976] [info] ajp_service::jk_ajp_common.c (2982): (cfusion) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)
[Sat Aug 21 10:55:11.830 2021] [5916:5976] [error] ajp_service::jk_ajp_common.c (3003): (cfusion) connecting to tomcat failed (rc=-3, errors=10, client_errors=0).
[Sat Aug 21 10:55:11.830 2021] [5916:5976] [error] HttpExtensionProc::jk_isapi_plugin.c (2734): service() failed with http error 503

Again, to fix, I simply revert back to v4.

CF seemed to be running fine on v11. The port 8018 was listening, and all the CF processes were running.

What am I missing

5 Comments
2021-08-24 09:44:54
2021-08-24 09:44:54

Suggestion: Ask your question in the ColdFusion forum. When you do, include a link to this page.

Like
(1)
>
BKBK
's comment
2021-08-24 14:32:03
2021-08-24 14:32:03
>
BKBK
's comment

Thanks! I was not successful in finding a specific forum for these questions.

Like
2021-08-24 06:45:08
2021-08-24 06:45:08

Hello,

As I recall Update 8 introduced a tomcat change where it was not bound to all interfaces but to localhost only. One needs to edit the server.xml to bind to TCP and workers.properties to match.

This section of  server.xml and workers EG:

-<Connector port=”8018″ protocol=”AJP/1.3″ packetSize=”65535″ redirectPort=”8451″ tomcatAuthentication=”false” maxThreads=”500″ connectionTimeout=”60000″ address=”10.0.0.1″/>

– worker.cfusion.host=10.0.0.1

Hope that helps, Carl.

 

 

 

Like
(1)
(2)
>
carl type3
's comment
2021-08-24 14:34:49
2021-08-24 14:34:49
>
carl type3
's comment

Thanks. I’ll give that a try. Just to make sure I understand (I’m a bit of a CF admin newbie), I would edit server.xml to have the IP address that matches what is in workers.properties after I run wsconfig.exe to point to the CF instance. Is that correct? Then I assume restart cfusion service to pick up the change.

Like
>
dawalkertiger
's comment
2021-08-25 15:25:44
2021-08-25 15:25:44
>
dawalkertiger
's comment

That might work. It wasn’t clear from Carl’s answer if he was saying HE had found that 10.0.0.1 value already in his workers.properties, and its worker.cfusion.host value. If so, then yes, you’d  at least want to edit your instance’s server.xml  to add or change the “address” attribute (on the AJP connector line specifically) to match.

And yes, you’d need to restart CF for that change to be picked up.

If somehow simply “making those match” doesn’t work, a problem could be that the value in that worker.cfusion.host (or worker.instancename.host, if using multiple instances) may not itself be right. That gets put there by a value selected or entered in the CF wsconfig tool.

And if there’s a domain name there, of course that would resolve to an ip address and THAT is what you’d need to put in as the address in the server.xml.

I will share that the best way to know “what” ip address to use may be to look at the isapi_redirect.log (in the folder where the workers.properties file is–and there may be more than one such folder under your cf config/wsconfig folder). For apache, it would be the mod_jk.log, in that folder or in one of your apache config folders.

In that log, you may see lines with errors along the lines of these (your port and:

[info] jk_open_socket::jk_connect.c (816): connect to 127.0.0.1:8018 failed

or another error line you may see is this (I show a different IP address, just to show it could appear as an ipv6 address):

[info] ajp_connect_to_endpoint::jk_ajp_common.c (1140): (cfusion) Failed opening socket to (::1:8018)

Whatever that ip address is, that is the value you should try to enter into the address field, then restart CF.

Let us know how it goes.

Like
Add Comment