Skip to main content
Pokermon
Inspiring
February 13, 2019
Answered

The Monitoring Service is not available after installing CF 2016 Update 8

  • February 13, 2019
  • 1 reply
  • 1077 views

Help please, I cannot get back into my COldfusion administator after installing the latest update...

"Error","localhost-startStop-1","02/13/19","09:56:09","","Unable to initialise Monitoring service: java.lang.NoClassDefFoundError: org/eclipse/jetty/server/Handler"

java.lang.NoClassDefFoundError: org/eclipse/jetty/server/Handler

at coldfusion.monitor.MonitoringServiceImpl.startJettyServer(MonitoringServiceImpl.java:196)

at coldfusion.featurerouter.handler.standard.StandardMonitoringServiceImpl.startJettyServer(StandardMonitoringServiceImpl.java:121)

at coldfusion.featurerouter.handler.standard.StandardMonitoringServiceImpl.start(StandardMonitoringServiceImpl.java:61)

at coldfusion.server.CFService.setupMonitoringService(CFService.java:494)

at coldfusion.server.CFService.start(CFService.java:724)

at coldfusion.server.j2ee.CFStartUpServlet.startCFService(CFStartUpServlet.java:567)

at coldfusion.server.j2ee.CFStartUpServlet.init(CFStartUpServlet.java:510)

at javax.servlet.GenericServlet.init(GenericServlet.java:158)

at coldfusion.bootstrap.ClassloaderHelper.initServletClass(ClassloaderHelper.java:121)

at coldfusion.bootstrap.BootstrapServlet.init(BootstrapServlet.java:59)

at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1144)

at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091)

at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:983)

at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5028)

at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5340)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)

at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1421)

at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1411)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

Caused by: java.lang.ClassNotFoundException: org.eclipse.jetty.server.Handler

at coldfusion.bootstrap.BootstrapClassLoader.loadClass(BootstrapClassLoader.java:252)

at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

... 22 more

"Error","Thread-19","02/13/19","09:56:40","","org.jpedal.fonts.FontMappings.setFontDirs([Ljava/lang/String;)V"

java.lang.NoSuchMethodError: org.jpedal.fonts.FontMappings.setFontDirs([Ljava/lang/String;)V

at coldfusion.document.JPedalFontRegistry.registerDirectories(JPedalFontRegistry.java:114)

at coldfusion.document.DocumentServiceImpl.initializeDocumentService(DocumentServiceImpl.java:291)

at coldfusion.document.DocumentServiceImpl.access$000(DocumentServiceImpl.java:86)

at coldfusion.document.DocumentServiceImpl$1.run(DocumentServiceImpl.java:252)

"Error","Thread-19","02/13/19","09:56:43","","The Monitoring service is not available. This exception is usually caused by service startup failure. Check your server configuration."

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

at coldfusion.server.ServiceFactory.getMonitoringService(ServiceFactory.java:223)

at coldfusion.document.DocumentServiceImpl.loadPDFgServiceManagers(DocumentServiceImpl.java:493)

at coldfusion.document.DocumentServiceImpl.initializeDocumentService(DocumentServiceImpl.java:335)

at coldfusion.document.DocumentServiceImpl.access$000(DocumentServiceImpl.java:86)

at coldfusion.document.DocumentServiceImpl$1.run(DocumentServiceImpl.java:252)

This topic has been closed for replies.
Correct answer Pokermon

I was able to install the update manually and it corrected the issue. FYI

1 reply

Pokermon
PokermonAuthorCorrect answer
Inspiring
February 13, 2019

I was able to install the update manually and it corrected the issue. FYI