[jboss-jira] [JBoss JIRA] (WFLY-12135) error deploying web service without http-listener (only https-listener)

[ https://issues.jboss.org/browse/WFLY-12135?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-12135: --------------------------------------- This is actually reported downstream as JBEAP-14818 -- linked now. The whole exception is: {noformat} 19:01:37,945 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."helloworld-ws.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."helloworld-ws.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "helloworld-ws.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IllegalStateException: WFLYUT0063: Could not find the port number listening for protocol HTTP/1.1 at org.wildfly.extension.undertow.WebServerService.getPort(WebServerService.java:68) at org.jboss.as.webservices.config.WebServerInfoImpl.getPort(WebServerInfoImpl.java:36) at org.jboss.ws.common.management.AbstractServerConfig.getConnectorPort(AbstractServerConfig.java:328) at org.jboss.ws.common.management.AbstractServerConfig.getWebServicePort(AbstractServerConfig.java:237) at org.jboss.wsf.spi.metadata.config.SOAPAddressRewriteMetadata.getWebServicePort(SOAPAddressRewriteMetadata.java:66) at org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect$PortValue.getPortValue(EndpointAddressDeploymentAspect.java:224) at org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect$PortValue.getValue(EndpointAddressDeploymentAspect.java:217) at org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect.start(EndpointAddressDeploymentAspect.java:84) at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176) ... 8 more {noformat} easily reproducible by removing http listener and deploying quickstart with WS. {noformat} /subsystem=undertow/server=default-server/http-listener=default:remove deploy ~/git/wildfly-quickstarts/helloworld-ws/target/helloworld-ws.war {noformat} The part of the problem is mismatch between how ws {{org.jboss.ws.common.management.AbstractServerConfig#getConnectorPort}} are trying to use the {{org.jboss.as.webservices.config.WebServerInfoImpl}}. The undertow implementation {{org.wildfly.extension.undertow.WebServerService#getPort}} is designed to consume values http/https/ajp rather than full protocol name. Moreover, I don't see a reason why WS are not defaulting to https when http is unavailable. -- This message was sent by Atlassian Jira (v7.12.1#712002)