Skip to main content
NetApp Knowledge Base

OnCommand Application installation fails to start Server Services due to port conflict with World Wide Web Publishing service

Views:
395
Visibility:
Public
Votes:
0
Category:
oncommand-insight
Specialty:
legacy
Last Updated:

Applies to

Any of the following OnCommand Applications installed on a Windows Host.

  • OnCommand Insight (OCI)
  • Data WareHouse (DWH)
  • OnCommand Unified Manager (UM)
  • OnCommand Workflow Automation (WFA)

Issue

  • Look at the CLI output of:> netstat -ano| findstr -i 80  you will we see:  SYSTEM (PID 4) is LISTENING on Port 80.  (the World Wide Web Publishing service starts as PID 4 by default)
  • The Deployment files all resolve as a .failed
  • Within the System Logs you could possibly see the following error at the beginning of the cascade of failures:

Services which failed to start: service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener.
20XX-XX-XX 16:05:17,892 INFO [org.jboss.as.connector.subsystems.datasources] (msc service thread 1-3) JBAS010409: Unbound Datasource [Java:/onaro_pool_acq]
20XX-XX-XX 16:05:17,908 INFO [org.jboss.as.connector.deployers.jdbc] (msc service thread 1-8) JBAS010418: Stopped Driver service with driver-name = h2
20XX-XX-XX 16:05:17,908 INFO [org.jboss.messaging] (msc service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
20XX-XX-XX 16:05:17,908 INFO [org.jboss.as.connector.subsystems.datasources] (msc service thread 1-4) JBAS010409: Unbound Datasource [Java:/onaro_pool]
20XX-XX-XX 16:05:17,908 INFO [org.wildfly.extension.undertow] (msc service thread 1-7) JBAS017521: Undertow HTTPS listener https suspending
20XX-XX-XX 16:05:17,923 INFO [org.jboss.as.connector.deployment] (msc service thread 1-1) : Unbound JCA ConnectionFactory [java:/JmsXA]
20XX-XX-XX 16:05:17,923 INFO [org.jboss.as.connector.messaging] (ServerService Thread Pool -- 67) JBAS011605:  Unbound messaging object to jndi name java:/queue/SummaryQueue

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.