portal entry

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

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

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

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

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

It would certainly be nice to hear from Adobe as to whether this issue was (or was to be) addressed by update 3. It would also be helpful to hear from anyone experiencing it, whether changing that heartbeat interval fixed it. And if so (for any where that fixed it), I would be curious to know: is the instance in question being monitored by the CF2018 PMT (a new monitor, which can be setup anywhere, whether on the same server as CF or elsewhere that can reach it). You can see if the instance is being monitored by visiting the new menu element in the CF 2018 Admin for the PMT. It lets you know if the instance is being monitored or not. I am curious to know if the users experiencing this issue (where changing the heartbeat helps) either ARE or are NOT having the PMT monitor the instance in question, in case that's significant. Also, note that there was an update to the PMT, that came WITH CF2018 update 2--but it is not applied automatically. You must do it manually. I have a blog post here on doing that: <a href="https://coldfusion.adobe.com/?p=4889">https://coldfusion.adobe.com/?p=4889</a> I'd be curious, as well, to know if those experiencing this issue maybe had NOT done that PMT update (as my understanding of the heartbeat interval is that it's related to the monitoring of the web connection by CF for the sake of the PMT).

Comment by Charlie Arehart

Annie, I know you solved the problem by making that change, but for the sake of completeness, could you give some consideration to <a href="https://coldfusion.adobe.com/2019/02/apache-crashes-serving-multiple-thread-requests-using-cf2018/#comment-32687">the comment I'd shared back on Feb 14</a> (after yours), asking if you had enabled the PMT (which is what the heartbeat is related to), and where I pointed out how there was an update to the PMT that was available? Even if you may feel the issue no longer applies for you, your answers could help others facing and finding this problem here.

Comment by Charlie Arehart