[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-railo-tomcat-8-error-and-solution-for-a-child-container-failed-during-start":3},{"id":4,"title":5,"body":6,"date":49,"description":12,"extension":50,"meta":51,"navigation":52,"path":53,"published":52,"seo":54,"slug":55,"stem":56,"summary":5,"tags":57,"__hash__":60},"blog/blog/2014-11-18-railo-tomcat-8-error-and-solution-for-a-child-container-failed-during-start.md","Railo / Tomcat 8 Error & Solution For (A child container failed during start)",{"type":7,"value":8,"toc":45},"minimark",[9,13,16,19,22,28,31,36,39,42],[10,11,12],"p",{},"I noticed a few days ago that a new update for Apache Tomcat 8 was released (8.0.15). Today I decided to go ahead and update my server but ran into a minor hiccup when trying to access my websites tied to Railo.",[10,14,15],{},"Usually, updating Tomcat 8 with one of it's minors is pretty straight forward. Download the new version, unzip and swap out the JAR files in the \"lib\" folder and restart Railo/Tomcat. Going from 8.0.14 to 8.0.15, not so much. At least for me. Everything in the console came back ok when I restarted Railo however, after checking one of my sites, I noticed I was getting 502's with no recovery.",[10,17,18],{},"To the Tomcat logs I went. Specifically the catalina.out log. What I found was a chain of exceptions that ultimately told me 2 things - Tomcat was failing to start and, after brief digging in those traces, it was due to a missing class.",[10,20,21],{},"Here's what I found:",[10,23,24],{},[25,26,27],"code",{},"SEVERE: A child container failed during start java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[my domain here].StandardContext[]]",[10,29,30],{},"A little further down the stack revealed this...",[10,32,33],{},[25,34,35],{},"Caused by: java.lang.ClassNotFoundException: org.apache.juli.WebappProperties",[10,37,38],{},"Which (after some googling) is a class inside of the tomcat-juli.jar in Tomcat's \"bin\" folder. This is not something I normally update; so I updated the JAR file, restarted Railo/Tomcat and, like magic, all of my sites were functioning as usual.",[10,40,41],{},"So there we have it. Hopefully this helps someone else out. An issue like this is definitely not specific to Railo so it could possibly strike any application running through Tomcat 8 after an update.",[10,43,44],{},"Happy coding!",{"title":46,"searchDepth":47,"depth":47,"links":48},"",2,[],"2014-11-14","md",{},true,"/blog/2014-11-18-railo-tomcat-8-error-and-solution-for-a-child-container-failed-during-start",{"title":5,"description":12},"railo-tomcat-8-error-and-solution-for-a-child-container-failed-during-start","blog/2014-11-18-railo-tomcat-8-error-and-solution-for-a-child-container-failed-during-start",[58,59],"CFML","Apache Tomcat","KENchXwHWkgiGea4AL22GcRCu2Tqk6NkT3ZgdO47gRk"]