Highlighted

Tomcat ISAPI_redirect.log errors - normal?

Engaged ,
Nov 18, 2014

Copy link to clipboard

Copied

Hi,

We have a mixture of CF10 and CF11 servers running on Windows 2012, IIS 8/8.5. On one CF10 server we have these errors consistently throughout the day in the isapi_redirect.log file:

[Tue Nov 18 08:58:50.130 2014] [10776:11284] [error] isapi_write_client::jk_isapi_plugin.c (1400): WriteClient failed with 1229 (0x000004cd)

[Tue Nov 18 08:58:50.281 2014] [10776:11284] [info] ajp_process_callback::jk_ajp_common.c (2089): Writing to client aborted or client network problems

[Tue Nov 18 08:58:50.356 2014] [10776:11284] [info] ajp_service::jk_ajp_common.c (2795): (cfusion) sending request to tomcat failed (unrecoverable), because of client write error (attempt=1)

[Tue Nov 18 08:58:50.416 2014] [10776:11284] [info] HttpExtensionProc::jk_isapi_plugin.c (2603): service() failed because client aborted connection

The connector is set to debug level INFO, yet we see INFO, WARN and ERROR status messages. We had this issue on CF10 update 12 and update 14.

Appreciate it someone could check their isapi_redirect.log log to see if they get these errors too. Are the errors normal (people closing connections with ESC key etc) or is there tuning to do, or is there a problem? Curiously, some of our servers have no such errors at all, except for the ISAPI connector starting up and shutting down and showing the number of connections etc. The only significant difference between the website with the errors and the ones without is that it uses more AJAX requests. Be grateful for any pointers.

Views

3.3K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Tomcat ISAPI_redirect.log errors - normal?

Engaged ,
Nov 18, 2014

Copy link to clipboard

Copied

Hi,

We have a mixture of CF10 and CF11 servers running on Windows 2012, IIS 8/8.5. On one CF10 server we have these errors consistently throughout the day in the isapi_redirect.log file:

[Tue Nov 18 08:58:50.130 2014] [10776:11284] [error] isapi_write_client::jk_isapi_plugin.c (1400): WriteClient failed with 1229 (0x000004cd)

[Tue Nov 18 08:58:50.281 2014] [10776:11284] [info] ajp_process_callback::jk_ajp_common.c (2089): Writing to client aborted or client network problems

[Tue Nov 18 08:58:50.356 2014] [10776:11284] [info] ajp_service::jk_ajp_common.c (2795): (cfusion) sending request to tomcat failed (unrecoverable), because of client write error (attempt=1)

[Tue Nov 18 08:58:50.416 2014] [10776:11284] [info] HttpExtensionProc::jk_isapi_plugin.c (2603): service() failed because client aborted connection

The connector is set to debug level INFO, yet we see INFO, WARN and ERROR status messages. We had this issue on CF10 update 12 and update 14.

Appreciate it someone could check their isapi_redirect.log log to see if they get these errors too. Are the errors normal (people closing connections with ESC key etc) or is there tuning to do, or is there a problem? Curiously, some of our servers have no such errors at all, except for the ISAPI connector starting up and shutting down and showing the number of connections etc. The only significant difference between the website with the errors and the ones without is that it uses more AJAX requests. Be grateful for any pointers.

Views

3.3K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Nov 18, 2014 0
Engaged ,
Nov 18, 2014

Copy link to clipboard

Copied

Wow, no one else has this problem?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 18, 2014 0
Guide ,
Nov 18, 2014

Copy link to clipboard

Copied

Hi,

I have seen similar details in ISAPI logs. I don't think it is a problem. Like you say not every site has it. I notice it more at locations that use tablet wireless devices so fair to say users disconnect unexpectedly rather than logout of CF based applications.

HTH, Carl.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 18, 2014 0
Engaged ,
Nov 19, 2014

Copy link to clipboard

Copied

Thanks Carl. Adobe say not to worry about them too, just strange how two seemingly identical setups can cause such a difference in errors. I wish Adobe would create a wiki (or something) just for Tomcat/ISAPI issues. These errors and logs are not explained at all, anywhere, by Adobe (to my knowledge). It just guesswork trying to work out what it all means and if there is an issue or not.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 19, 2014 0
Adobe Employee ,
Nov 19, 2014

Copy link to clipboard

Copied

Yes, you can ignore these errors. These are from Tomcat only and will not affect ColdFusion functionality.

Regards,

Anit Kumar

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 19, 2014 0
Enthusiast ,
Nov 20, 2014

Copy link to clipboard

Copied

Yes, you can ignore these errors.

Also, if you have recently applied update 14 on ColdFusion 10 then re-create connector and perform the CF tuning with IIS. You can follow this blog : http://blogs.coldfusion.com/post.cfm/coldfusion-11-iis-connector-tuning

NOTE : The blog is for CF 11 however is applicable for CF 10 and CF 11 both. Also, perform the above in the maintenance window.

Hopefully, after performing the above you will not see these errors

Thanks

VJ


Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 20, 2014 0
Engaged ,
Nov 20, 2014

Copy link to clipboard

Copied

@Vishu, thanks for the reply, but.... it's so  vague. What do we "tune" in particular?

Also, we will lose these settings when we run wsconfig again, will we not?

Please tell us what to try and what our errors imply we should tune. Are you suggesting we just try every single combination of options until the errors hopefully go away? If so, that is really bad advice (sorry).

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 20, 2014 0
Enthusiast ,
Nov 20, 2014

Copy link to clipboard

Copied

I have seen these errors only once in one of the test servers and I performed the same which I shared with you. So, I shared my experience with you.

Before recreating the connector, you can always take the backup of wsconfig folder

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 20, 2014 0
Engaged ,
Nov 21, 2014

Copy link to clipboard

Copied

"and I performed the same which I shared with you"

Performed what Vish? I read the connector tuning link, but what is not clear is what we need to tune in light of these errors. If you can give a clue it would be helpful or we could waste days trying all sorts of things. If you had these errors and tuned the connector to remove them, cannot you share the adjustments you made with the community please?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 21, 2014 0
New Here ,
Nov 22, 2014

Copy link to clipboard

Copied

We too are experiencing many of these problems with tomcat connector version 12.40, in ColdFusion 11, update 3 (release of update 3).  Adobe, please fix!

[Sat Nov 22 10:19:50.673 2014] [12496:7932] [info] HttpExtensionProc::jk_isapi_plugin.c (2603): service() failed because client aborted connection

[Sat Nov 22 10:20:14.120 2014] [12496:5460] [error] isapi_write_client::jk_isapi_plugin.c (1400): WriteClient failed with 1229 (0x000004cd)

[Sat Nov 22 10:20:14.120 2014] [12496:5460] [info] ajp_process_callback::jk_ajp_common.c (2089): Writing to client aborted or client network problems

[Sat Nov 22 10:20:14.121 2014] [12496:5460] [info] ajp_service::jk_ajp_common.c (2795): (cfusion) sending request to tomcat failed (unrecoverable), because of client write error (attempt=1)

[Sat Nov 22 10:20:14.121 2014] [12496:5460] [info] HttpExtensionProc::jk_isapi_plugin.c (2603): service() failed because client aborted connection

[Sat Nov 22 10:20:14.417 2014] [12496:11856] [error] isapi_write_client::jk_isapi_plugin.c (1400): WriteClient failed with 1229 (0x000004cd)

[Sat Nov 22 10:20:14.418 2014] [12496:11856] [info] ajp_process_callback::jk_ajp_common.c (2089): Writing to client aborted or client network problems

[Sat Nov 22 10:20:14.418 2014] [12496:11856] [info] ajp_service::jk_ajp_common.c (2795): (cfusion) sending request to tomcat failed (unrecoverable), because of client write error (attempt=1)

[Sat Nov 22 10:20:14.418 2014] [12496:11856] [info] HttpExtensionProc::jk_isapi_plugin.c (2603): service() failed because client aborted connection

[Sat Nov 22 10:20:16.908 2014] [12496:5352] [error] isapi_write_client::jk_isapi_plugin.c (1400): WriteClient failed with 1229 (0x000004cd)

[Sat Nov 22 10:20:16.908 2014] [12496:5352] [info] ajp_process_callback::jk_ajp_common.c (2089): Writing to client aborted or client network problems

[Sat Nov 22 10:20:16.909 2014] [12496:5352] [info] ajp_service::jk_ajp_common.c (2795): (cfusion) sending request to tomcat failed (unrecoverable), because of client write error (attempt=1)

[Sat Nov 22 10:20:16.909 2014] [12496:5352] [info] HttpExtensionProc::jk_isapi_plugin.c (2603): service() failed because client aborted connection

[Sat Nov 22 10:20:20.104 2014] [12496:13652] [error] isapi_write_client::jk_isapi_plugin.c (1400): WriteClient failed with 1229 (0x000004cd)

[Sat Nov 22 10:20:20.104 2014] [12496:13652] [info] ajp_process_callback::jk_ajp_common.c (2089): Writing to client aborted or client network problems

[Sat Nov 22 10:20:20.105 2014] [12496:13652] [info] ajp_service::jk_ajp_common.c (2795): (cfusion) sending request to tomcat failed (unrecoverable), because of client write error (attempt=1)

[Sat Nov 22 10:20:20.105 2014] [12496:13652] [info] HttpExtensionProc::jk_isapi_plugin.c (2603): service() failed because client aborted connection

[Sat Nov 22 10:20:21.942 2014] [12496:12500] [error] isapi_write_client::jk_isapi_plugin.c (1400): WriteClient failed with 995 (0x000003e3)

[Sat Nov 22 10:20:21.943 2014] [12496:12500] [info] ajp_process_callback::jk_ajp_common.c (2089): Writing to client aborted or client network problems

[Sat Nov 22 10:20:21.944 2014] [12496:12500] [info] ajp_service::jk_ajp_common.c (2795): (cfusion) sending request to tomcat failed (unrecoverable), because of client write error (attempt=1)

[Sat Nov 22 10:20:21.944 2014] [12496:12500] [info] HttpExtensionProc::jk_isapi_plugin.c (2603): service() failed because client aborted connection

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 22, 2014 0
Adobe Employee ,
Nov 22, 2014

Copy link to clipboard

Copied

Can you let us know, how these entries are impacting your server? As mentioned earlier, you can ignore these errors. These are from Tomcat only and will not affect ColdFusion functionality.

Regards,

Anit Kumar

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 22, 2014 0
New Here ,
Nov 22, 2014

Copy link to clipboard

Copied

That's not true, these errors cannot be ignored.  It is causing graphic files on the web site to not display properly, intermittently.  I refresh the page, some display, some don’t.  I right click on a problem graphic, get its url, surf to the graphic itself, and blank comes up.  No 404 error, no error of any kind, just blank.  Also, I’m observing a large number of active requests pooling up and not getting served successfully.  I switched back to the boncode connector and all these problems went away immediately.  Issue definitely points to problems with the Tomcat connector.

We are running ColdFusion 11 Enterprise update 3 (version posted on November 19th 2014, with tomcat 12.40).

Regards,

Claire

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 22, 2014 0
New Here ,
Nov 22, 2014

Copy link to clipboard

Copied

Issues observed with Boncode connector as well (active requests pooling up), switched back to Tomcat connector just now.  The same errors are continuing now in the tomcat log as seen before.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 22, 2014 0
Engaged ,
Nov 22, 2014

Copy link to clipboard

Copied

"Can you let us know, how these entries are impacting your server?"

Anit, we wish we knew, which is why we are asking you. If we see these errors a lot, are end-users seeing a problem too? It seems likely, but unless we know what the errors actually mean and how we can "tune" them away (see Vish's answer above) how can we tackle this. You say ColdFusion is not affected, but how can you guarantee that? Is ignoring errors really advisable?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 22, 2014 0
Adobe Employee ,
Nov 27, 2014

Copy link to clipboard

Copied

As mentioned earlier, ColdFusion functionality will not be affected in any way. If a user who requests for a site breaks connection in between like closing the browser, these errors will be logged. Users should simply ignore them, there is nothing wrong here.

If the server is taking too long to respond then there are chances that, the browser itself will close the connection. So you can track/log the slow running requests and see if these errors are generated for them only.


Regards,

Anit Kumar

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 27, 2014 0
Engaged ,
Nov 27, 2014

Copy link to clipboard

Copied

Hi Anit,

The problem is that we cannot stop the errors from being reported. Why is it that the log level is INFO yet we see ERROR, WARN and INFO? How can we make it just report INFO?On other servers we have INFO log level and only see INFO. Also, we do not see the errors anywhere else. Surely another busy website would get some of the same errors? But no, not one. We have 4 cf 10 websites and there is not one of these errors. The server  that has the error is the one with the "fixed" connector.

This all points to a buggy connector Anit.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 27, 2014 0
Adobe Employee ,
Nov 27, 2014

Copy link to clipboard

Copied

This is not something specific to CF11. It is the same behaviour since CF10, rather since we started using Tomcat. When a connection is terminated/breaks on the browser, the error gets logged by Tomcat. What I have been trying to say so far is, these errors will NOT impact anything on the servers. If there are issues with your server, then there is a strong possibility that they are most likely caused due to something else.

Having issues with your server, send the complete details with Setting summary from CF Admin, connector logs (log level set to "debug") and CF logs to cfinstal<AT>adobe<DOT>com. We will have a look on therm, then.

Regards,

Anit Kumar

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 27, 2014 0
Engaged ,
Nov 27, 2014

Copy link to clipboard

Copied

Can you please tell me why debug_level INFO does not work, please.  That would stop these massive logs and this would solve the issue, at least. Setting the connector to DEBUG will not tell us why the thing won't ignore non-INFO errors, will it?

thank you.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 27, 2014 0
Guide ,
Nov 27, 2014

Copy link to clipboard

Copied

Hi,

You could roll the ISAPI log so as not to grow log size.

Edit isapi_redirect.properties:

log_file= ...\1\isapi_redirect_%d-%m-%Y.log

log_rotationtime= 86400       EG 1 day

=604800        (1 week)

=18144000    (1 month)

HTH, Carl.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 27, 2014 1
Engaged ,
Nov 27, 2014

Copy link to clipboard

Copied

Yes I thought of that, thanks Carl. Is there a way to disable logging?

Have you seen a connector that logs events it shouldn't? I mean if I specify debug_level INFO, I expect not to see ERROR and WARN events. Is that reasonable?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 27, 2014 0
Guide ,
Nov 27, 2014

Copy link to clipboard

Copied

I just tried this and found it worked, no log file to read. Not sure it is the best idea.

log_file= D:\ColdFusion10\config\wsconfig\1\nul

Regards, Carl.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 27, 2014 0
Engaged ,
Nov 27, 2014

Copy link to clipboard

Copied

lol good one Carl, you know more than Adobe about logging it seems. Isn't NUL a special DOS device name, I recall? Rather like /dev/null on *nix systems.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 27, 2014 0
Guide ,
Nov 27, 2014

Copy link to clipboard

Copied

Options Log level= debug, info, warn, error or trace

Tend to find with CF they all displayed the same output except debug which is very verbose.

True like /dev/null

Till next time, Carl.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 27, 2014 0
tribule LATEST
Engaged ,
Nov 27, 2014

Copy link to clipboard

Copied

Hmm, not much point in having a log_level directive then in that case. On all of our servers the log_level is adhered to, except one. Might have something to do with individual/all connectors, or a buggy connector perhaps.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 27, 2014 0