Skip to main content
Participant
March 30, 2021
Question

ColdFusion 2016 won't start after Update 17

  • March 30, 2021
  • 1 reply
  • 1313 views

Udpate 16 was working fine, after applying Update 17, ColdFusion Application Service no longer starts properly. 

 

Browsers get 500 Internal Server Error

coldfusion.server.ServiceFactory$ServiceNotAvailableException: The Runtime service is not available.

 

From the logs and cfstart console output:

Mar 28, 2021 22:26:19 PM Error [localhost-startStop-1] - Unable to initialise Security service: java.lang.NoSuchFieldError: TRACE
java.util.MissingResourceException: Can't find resource key "CFStartUpServlet.notInitialised" in base name coldfusion/server/j2ee/resource.properties

 

Mar 28, 2021 10:26:19 PM org.apache.catalina.core.StandardContext loadOnStartup
SEVERE: Servlet [ColdFusionStartUpServlet] in web application [] threw load() exception
java.util.MissingResourceException: Can't find resource key "CFStartUpServlet.notInitialised" in base name coldfusion/server/j2ee/resource.properties

Any ideas from this forum? 

    This topic has been closed for replies.

    1 reply

    Charlie Arehart
    Community Expert
    Community Expert
    March 30, 2021

    Bummer that you're experiencing this. But it can happen.

     

    First, I suspect the problem is not what the error messages there show, but ones that happened BEFORE them in the startup of CF. Can you report what is the FIRST error upon startup, in the coldfusion-error.log and coldfusion-out.log? Or can you confirm these are indeed the first?

     

    As for such errors, often it's not BECAUSE of the update but due to something else. For example, it may be that CF had not been restarted for days or weeks, and something could have changed in the CF configuration files leading to such an error.

     

    If you may be running CF as a service, you may also want to try running it from the command prompt. In the cfusion/bin folder is a cfstart script. Stop the CF service and then run that. Do you get any different result there? You may not, but it's worth a try.

     

    I will say that if you have trouble solving this on your own, I have helped people with such problems about weekly, and again there can be any of many causes and solutions. If you would rather it get resolved ASAP, I can offer help via direct remote screensharing (or even just over the phone if necessary). Find more in the consulting page at carehart.org.

     

    But otherwise, we can keep trying here (and others may well chime in with new thoughts for you).

    /Charlie (troubleshooter, carehart. org)
    May 12, 2021

    Hello!

    I am experiencing a very similar symptom as the OP's with the difference being that I'm trying to upgrade CF2018 with hotfix 11.

    The coldfusion-out.log is pretty bare with just these few lines after startup:

    05/11 14:59:14 INFO License Service: Flex 1.5 CF Edition enabled
    05/11 14:59:14 INFO Starting Flex 1.5 CF Edition
    May 11, 2021 14:59:15 PM Information [main] - Starting logging...
    May 11, 2021 14:59:15 PM Information [main] - Starting license...
    May 11, 2021 14:59:15 PM Information [main] - Evaluation Edition enabled
    May 11, 2021 14:59:15 PM Information [main] - Starting crypto...
    May 11, 2021 14:59:15 PM Information [main] - Installed JSafe JCE provider: Version 3.6 RSA Security Inc. Crypto-J JCE Security Provider (implements RSA, DSA, Diffie-Hellman, AES, DES, Triple DES, DESX, RC2, RC4, RC5, PBE, MD2, MD5, RIPEMD160, SHA1, SHA224, SHA256, SHA384, SHA512, HMAC-MD5, HMAC-RIPEMD160, HMAC-SHA1, HMAC-SHA224, HMAC-SHA256, HMAC-SHA384, HMAC-SHA512)
    May 11, 2021 14:59:15 PM Information [main] - Starting security...
    May 11, 2021 14:59:16 PM Error [main] - Unable to initialise Security service: java.lang.NoSuchFieldError: TRACE
    05/11 14:59:16 INFO Macromedia Flex Build: 87315.134646

    The coldfusion-error.log has coupld warnings but the first error is what the OP listed (note that this seems to be the CF program logging the error from Catalina but immediately afterwards the CF program throws an error with the same stack trace):

    May 11, 2021 2:59:14 PM org.apache.catalina.core.ApplicationContext log
    INFO: ColdFusionStartUpServlet: ColdFusion: VM version = 25.271-b25
    java.util.MissingResourceException: Can't find resource key "CFStartUpServlet.notInitialised" in base name coldfusion/server/j2ee/resource.properties
    	at coldfusion.util.RB.getString(RB.java:156)
    	at coldfusion.util.RB.getMessage(RB.java:618)
    	at coldfusion.util.RB.getString(RB.java:340)
    	at coldfusion.server.j2ee.CFStartUpServlet.init(CFStartUpServlet.java:519)
    	at javax.servlet.GenericServlet.init(GenericServlet.java:158)
    ...

    When you try to hit any CF pages, including the CFAdmin page, you get the following error:

    May 11, 2021 2:59:17 PM org.apache.catalina.core.StandardContext loadOnStartup
    SEVERE: Servlet [ServerCFCServlet] in web application [] threw load() exception
    coldfusion.server.ServiceFactory$ServiceNotAvailableException: The Runtime service is not available.
    	at coldfusion.server.ServiceFactory.getRuntimeService(ServiceFactory.java:121)
    	at coldfusion.cfc.ServerCFCServlet.init(ServerCFCServlet.java:31)
    	at javax.servlet.GenericServlet.init(GenericServlet.java:158)
    	at coldfusion.bootstrap.ClassloaderHelper.initServletClass(ClassloaderHelper.java:121)
    	at coldfusion.bootstrap.BootstrapServlet.init(BootstrapServlet.java:111)
    	at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1122)
    ...

    I tried as you suggested to stop the service and run the cfstart.bat script but I still get 500s and the console shows the same errors as the coldfusion-out.log and coldfusion-error.log files contain when using the service.

    Not sure if that little bit of extra information means much.

    Thanks in advance!

    Huajun

    Participant
    May 12, 2021

    Hello Huajun, we found some jar files in WEB-INF/lib that were causing our issue with HF17. Specifically it was a log4j.jar file that had been there for years and for whatever reason was not working after HF17. Unfortunately none of the log files indicated anything like this but Adobe support was finally able to pinpoint this as the issue. It took a few weeks of back and forth troubleshooting with them, but in the end they were able to help us.