tracker issue : CF-3123609

Problem Description: As the subject states, I have never seen this before 9.0.01 when deploying another instance. And I can also confirm that a fresh install of CF9 and deploy a new instance doesn't do this. Only once the updater 1 and other hotfixes have been applied does this error now happen.

ROOT CAUSE: 
coldfusion.server.ServiceFactory$ServiceNotAvailableException: The Monitoring service is not available.
	at coldfusion.server.ServiceFactory.getMonitoringService(ServiceFactory.java:221)
	at coldfusion.CfmServlet.service(CfmServlet.java:180)
	at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)
	at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)
	at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42)
	at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
	at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
	at jrun.servlet.FilterChain.service(FilterChain.java:101)
	at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
	at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
	at jrun.servlet.JRunRequestDispatcher.invokeNext(JRunRequestDispatcher.java:586)
	at jrun.servlet.JRunRequestDispatcher.forwardInvoke(JRunRequestDispatcher.java:555)
	at jrun.servlet.JRunRequestDispatcher.forward(JRunRequestDispatcher.java:203)
	at jrun.servlet.file.FileServlet.service(FileServlet.java:323)
	at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
	at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
	at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)
	at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
	at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172)
	at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
	at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)


Steps to Reproduce:

Actual Result:

Expected Result:

Any Workarounds: Yes delete the neo-monitoring after stopping the instance, and then restart the instance. However this is not something that we should be doing as an Administrator. It should not occur at all.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3123609

External Customer Info:
External Company:  
External Customer Name: ascott67
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments: