tracker issue : CF-3318699

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

Tomcat connector, isapi_redirector 1.2.32 issues

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/NotABug

Reporter/Name(from Bugbase): constantine vu / constantine vu (constantine.vu)

Created: 08/27/2012

Components: Installation/Config, Connector

Versions: 10.0

Failure Type: Crash

Found In Build/Fixed In Build: - /

Priority/Frequency: Critical / Some users will encounter

Locale/System: English / Win 2003 Server x64

Vote Count: 0

Problem Description: When install MS C++ redistribution update version 9.0.30729.17, isapi_redirector crashes intermittenly.  Also when admin account logoffs server, isapi_redirector also crashes 

Steps to Reproduce:install MS C++ update version 9.0.30729.17

Actual Result: isapi_redirector crashes with log: jk_open_socket::jk_connect.c(2268): connect to 127.0.0.1:8012 failed (errno=61) . .  .. 

Expected Result: isapi_redirector crashes with log: jk_open_socket::jk_connect.c(2268): connect to 127.0.0.1:8012 failed (errno=61) . .  

Any Workarounds: none

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3318699

External Customer Info:
External Company:  
External Customer Name: cvu@chugach-ak.com
External Customer Email:  
External Test Config: My Hardware and Environment details: windows server 2003 x64, all MS C++ 2005 and 2008, 2010 redistribution security updates and patches installed

Attachments:

Comments:

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.
Comment by External U.
18280 | August 30, 2012 09:57:59 AM GMT
The issue is not reproducible on our end. Installing MS C++ redistribution versions 9 / 10 / 11 does not interrupt ColdFusion. Is there a setup / logs we can look at?
Comment by Immanuel N.
18281 | August 21, 2014 06:53:18 AM GMT
Closing the bug as "Not a Bug" since we were not able to reproduce the issue at our end, and did not receive any additional information from the customer. If this bug still exists on your environment, please report back, and we will be reopening this bug.
Comment by Immanuel N.
18282 | December 03, 2014 01:59:44 AM GMT