portal entry

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

Apache crashes while serving multiple thread requests using CF2018

| View in Portal
February 08, 2019 01:52:14 PM GMT
5 Comments
<p>Apache crashes when there's multi-thread request in a web app server with CF2018 & Apache 2.4.</p>
<p>The post <a rel="nofollow" href="https://coldfusion.adobe.com/2019/02/apache-crashes-serving-multiple-thread-requests-using-cf2018/">Apache crashes while serving multiple thread requests using CF2018</a> appeared first on <a rel="nofollow" href="https://coldfusion.adobe.com">ColdFusion</a>.</p>
Labels: CF2018 Updates, ColdFusion 2018, Question, cf2018 updates, ColdFusion, coldfusion 2018, question

Comments:

Even after installing the ColdFusion2018 update 2, the apache crashes the above mentioned scenario. Hence we had to change the heartbeat_interval=0 in the workers.properties. Could Adobe CF technical team, look into this issue?
Comment by Annie Theogaraj
1738 | February 14, 2019 12:00:39 PM GMT
Annie, did you upgrade the apache connector for cf, as was indicated in this update's tech note? It would be easy to miss. And did you confirm that there are no errors in the update log created for you in the cfusion/hf-updates and the subdolder for this update? These things may show this is not a "bug" in the update as it may seem.
Comment by Charlie Arehart
1735 | February 14, 2019 02:08:44 PM GMT
Hi Charlie, There were no errors in the update log and the apache connector was upgraded and the SELinux context was applied as usual to the mod_jk.conf and workers.properies. The apache started as usual, and the application seems to be working fine. CFAdmin is accessible. On changing the heartbeat_interval=0, the apache stopped crashing. Annie
Comment by Annie Theogaraj
1731 | February 14, 2019 04:11:27 PM GMT
OK, thanks for the clarification, Annie. (I will assume by "no errors" in the update log that you mean not just that you "didn't see any at the bottom", but specifically that you had looked at the table near the top, tracking successes and errors, and it shows there were zero fatal or non-fatal errors.) And I missed that you said that changing the heartbeat_interval DID help solve things, as a workaround. That's interesting. Hope someone at Adobe may come to a solution for you soon, as it could affect others. I've not heard this elsewhere yet, myself. (There seems quite a few different issues with the latest update--affecting some though not all. But since it was an update across all 3 supported CF versions, they will likely have their hands full addressing such issues in the coming hours and days.)
Comment by Charlie Arehart
1730 | February 14, 2019 04:17:18 PM GMT
Your assumption is right. There are 0 FatalErrors and 0 NonFatalErrors. Someone from Adobe said that the bug is fixed in the CF2018, update 2. But its still happening and the workaround helps. There's a bug raised with them. Hope there's a solution for this. Thanks for your prompt response. Annie
Comment by Annie Theogaraj
1693 | February 18, 2019 12:19:04 PM GMT