<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Deepak Sir</title>
    <description>The latest articles on DEV Community by Deepak Sir (@deepak_sir__).</description>
    <link>https://dev.to/deepak_sir__</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3924748%2F642b10f5-bbca-46b4-93f8-0c9031ef7b65.png</url>
      <title>DEV Community: Deepak Sir</title>
      <link>https://dev.to/deepak_sir__</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/deepak_sir__"/>
    <language>en</language>
    <item>
      <title>ColdFusion Server Not Starting After Windows Update</title>
      <dc:creator>Deepak Sir</dc:creator>
      <pubDate>Wed, 13 May 2026 07:34:17 +0000</pubDate>
      <link>https://dev.to/deepak_sir__/coldfusion-server-not-starting-after-windows-update-1ijp</link>
      <guid>https://dev.to/deepak_sir__/coldfusion-server-not-starting-after-windows-update-1ijp</guid>
      <description>&lt;p&gt;&lt;strong&gt;Introduction&lt;/strong&gt;&lt;br&gt;
The Windows update notification appeared on Tuesday evening. You scheduled the patch installation for the maintenance window. The server rebooted at 2 AM as planned. By 6 AM, monitoring alerts started firing. The ColdFusion service is stopped. Starting it from the Services console produces a generic “service did not respond” error. The Event Viewer shows nothing useful. The CFAdmin login page returns connection refused. Every application that depended on this server is down.&lt;br&gt;
&lt;strong&gt;&lt;a href="https://medium.com/@Coding-Algorithms/coldfusion-server-not-starting-after-windows-update-e44fed506708" rel="noopener noreferrer"&gt;Read More&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>coldfusion</category>
      <category>coding</category>
      <category>ai</category>
      <category>technology</category>
    </item>
    <item>
      <title>Fix ColdFusion Application Scope Resets</title>
      <dc:creator>Deepak Sir</dc:creator>
      <pubDate>Tue, 12 May 2026 05:38:07 +0000</pubDate>
      <link>https://dev.to/deepak_sir__/fix-coldfusion-application-scope-resets-1h58</link>
      <guid>https://dev.to/deepak_sir__/fix-coldfusion-application-scope-resets-1h58</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fkxqhksvrjuvgz5ckeneo.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fkxqhksvrjuvgz5ckeneo.png" alt=" " width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;ColdFusion application scope variables reset unexpectedly for five primary documented reasons: the application’s idle timeout (this.applicationTimeout) expires; two Application.cfc files share the same this.name, causing them to overwrite each other's application scope; the JVM restarts due to memory exhaustion or unhandled errors; a clustered deployment maintains independent application scopes per instance with no cross-instance synchronization; and a manual or accidental applicationStop() call wipes the scope mid-session. The fix requires understanding that application scope lives in JVM memory only — it has no persistence beyond the running process.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://medium.com/@Coding-Algorithms/coldfusion-application-scope-variables-resetting-unexpectedly-configuration-and-production-ready-907fe89904b0" rel="noopener noreferrer"&gt;Read More&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>coldfusion</category>
      <category>software</category>
      <category>server</category>
      <category>architecture</category>
    </item>
  </channel>
</rss>
