Recently upgraded from Win 2012 Server to Win 2019 Server and from ColdBox 4 to ColdBox 5.3. No significant code changes.
Every day or so, ColdBox “dies”. This is new behavior since upgrades. The Lucee server is still working fine (I can access the admin pages, for instance), but I can’t access any page that references the ColdBox “app” cache (which is every page on our site).
I believe the relevant error information is below when trying to get an item from the app cache. If I restart the Lucee service, everything goes back to normal until it crashes again.
Thanks in advance for any insight someone can provide as to where to look next for issues.
{ “EXCEPTIONBEAN”: { “exceptionStruct”: { “Extended_Info”: “”, “Message”: “java.lang.InterruptedException”, “Detail”: “”, “additional”: {}, “TagContext”: [ { “Raw_Trace”: “coldbox.system.cache.cachefactory_cfc$cf.udfCall1(/coldbox/system/cache/CacheFactory.cfc:189)”, “codePrintPlain”: “187: \t<cfargument name=“name” required=“true” hint=“The named cache to retrieve”/>\n188: \n189: \t\t<cflock name=”#instance.lockName#" type=“readonly” timeout=“20” throwontimeout=“true”>\n190: \t\t\t<cfif structKeyExists(instance.caches, arguments.name)>\n191: \t\t\t\t<cfreturn instance.caches[ arguments.name ]>\n", “column”: 0, “line”: 189, “template”: “C:\Vat19\coldbox\system\cache\CacheFactory.cfc”, “id”: “??”, “type”: “cfml”, “codePrintHTML”: “187: \t<cfargument name=“name” required=“true” hint=“The named cache to retrieve”/>
\n188:
\n189: \t\t<cflock name=”#instance.lockName#" type=“readonly” timeout=“20” throwontimeout=“true”>
\n190: \t\t\t<cfif structKeyExists(instance.caches, arguments.name)>
\n191: \t\t\t\t<cfreturn instance.caches[ arguments.name ]>
\n" },