Skip to main content
Participant
February 5, 2018
Question

CF2016 Developer Edition on Websphere 8.5.5

  • February 5, 2018
  • 3 replies
  • 1051 views

I have deployed the cfusion.ear file that got created during the ColdFusion 2016 install.  I'm trying to get to ColdFusion admin and I'm receiving the exception below.  Has anyone ran into this.  I have tried running the hotfix, but still get same error.

Operating System:  Windows 64bit

[2/5/18 9:37:11:675 CST] 000000a0 webapp        E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[CfmServlet]: javax.servlet.ServletException: ROOT CAUSE:

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

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

at coldfusion.CfmServlet.service(CfmServlet.java:199)

at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)

at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1233)

at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:782)

at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)

at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)

at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136)

at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97)

at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42)

at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)

at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)

at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)

at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:967)

at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107)

at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3980)

at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)

at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1016)

at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1817)

at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:463)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:530)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:316)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:287)

at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)

at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)

at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)

at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)

at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)

at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)

at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)

at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)

at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)

at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)

at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:70)

at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)

at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)

at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)

at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:967)

at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107)

at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3980)

at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)

at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1016)

at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1817)

at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:463)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:530)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:316)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:287)

at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)

at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)

at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)

at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)

at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)

at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)

at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)

at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)

at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)

at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)

This topic has been closed for replies.

3 replies

Charlie Arehart
Community Expert
Community Expert
April 11, 2018

Patrick, what similarities do you share with the opportunity, Matthew? Are you also on websphere? Also getting this on initial launch of the cf admin?

If not a new install, then what changesd before things failed? Have you perhaps recently applied a cf or jvm update? Had a recent crash?

Any of the above could be clues to your resolution 

/Charlie (troubleshooter, carehart. org)
Participant
April 11, 2018

Hi,

Yes,I have the exact same issue. New install on Websphere 8.5.5. Trying to access the admin.

Priyank Shrivastava.
Community Manager
Community Manager
April 11, 2018

Hi Patrick,

I have deployed WAS8.5.5.13 with Java 8 and it worked without any issue. Unfortunately, I never got a chance to work with Matthew.

I received your email, I will be working with you on this.

Thanks,

Priyank

Thanks, Priyank Shrivastava
Participant
April 11, 2018

@priyanks97293812 did you get this resolved? I am having the same issue 

Priyank Shrivastava.
Community Manager
Community Manager
February 6, 2018

Hi,

May I know the IBM JDK which you are using with WAS 8.5.5?

Thanks,

Priyank Shrivastava

Thanks, Priyank Shrivastava
Participant
February 6, 2018

Hello Priyank,

Thank you for your response. Here is my java version:

Java version = 1.8.0, Java Runtime Version = pwa6480sr3fp20ifx-20161110_01

(SR3 FP20IV90630IV90578), Java Compiler = j9jit28, Java VM name = IBM J9

VM

Thank you,

Matt

On Tue, Feb 6, 2018 at 9:21 AM, priyanks97293812 <forums_noreply@adobe.com>

Priyank Shrivastava.
Community Manager
Community Manager
February 7, 2018

Hi Matt,

Have you recently updated the Java in your WAS server?

Thanks,

Priyank Shrivastava

Thanks, Priyank Shrivastava