[JBoss JIRA] (WFLY-3913) HTTPS socket-binding definition always needed
by Jose Monreal (JIRA)
[ https://issues.jboss.org/browse/WFLY-3913?page=com.atlassian.jira.plugin.... ]
Jose Monreal commented on WFLY-3913:
------------------------------------
Tomaz, what's wrong with my configuration file? I still don't understand what you are trying to tell me.
> HTTPS socket-binding definition always needed
> ---------------------------------------------
>
> Key: WFLY-3913
> URL: https://issues.jboss.org/browse/WFLY-3913
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final
> Reporter: Jose Monreal
> Assignee: Tomaz Cerar
> Labels: https, standalone
> Fix For: 8.2.0.CR1, 9.0.0.CR1
>
> Attachments: standalone.xml
>
>
> When removing HTTPS socket-binding from the standalone.xml file, the server start's in errors.
> The errors are the following:
> {noformat}
> 13:55:32,002 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("http-listener" => "default")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]}
> 13:55:32,005 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.ws.config"],
> "Services that may be the cause:" => [
> "jboss.binding.https",
> "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
> ]
> }}
> 13:55:32,007 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "ejb3"),
> ("service" => "remote")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]}
> 13:55:32,074 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.binding.https (missing) dependents: [service jboss.undertow.listener.default]
> service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector]
>
> 13:55:32,085 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.1.0.Final "Kenny" started (with errors) in 3475ms - Started 197 of 252 services (3 services failed or missing dependencies, 78 services are lazy, passive or on-demand
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (WFLY-3913) HTTPS socket-binding definition always needed
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3913?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-3913:
-----------------------------------
ejb3 & remoting subsystem.
> HTTPS socket-binding definition always needed
> ---------------------------------------------
>
> Key: WFLY-3913
> URL: https://issues.jboss.org/browse/WFLY-3913
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final
> Reporter: Jose Monreal
> Assignee: Tomaz Cerar
> Labels: https, standalone
> Fix For: 8.2.0.CR1, 9.0.0.CR1
>
> Attachments: standalone.xml
>
>
> When removing HTTPS socket-binding from the standalone.xml file, the server start's in errors.
> The errors are the following:
> {noformat}
> 13:55:32,002 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("http-listener" => "default")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]}
> 13:55:32,005 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.ws.config"],
> "Services that may be the cause:" => [
> "jboss.binding.https",
> "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
> ]
> }}
> 13:55:32,007 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "ejb3"),
> ("service" => "remote")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]}
> 13:55:32,074 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.binding.https (missing) dependents: [service jboss.undertow.listener.default]
> service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector]
>
> 13:55:32,085 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.1.0.Final "Kenny" started (with errors) in 3475ms - Started 197 of 252 services (3 services failed or missing dependencies, 78 services are lazy, passive or on-demand
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (WFLY-3913) HTTPS socket-binding definition always needed
by Jose Monreal (JIRA)
[ https://issues.jboss.org/browse/WFLY-3913?page=com.atlassian.jira.plugin.... ]
Jose Monreal commented on WFLY-3913:
------------------------------------
Tomaz, thanks for your help.
What do you mean by " fix the remoting configuration as your configuration is in between http-remoting and remoting" where's that?
> HTTPS socket-binding definition always needed
> ---------------------------------------------
>
> Key: WFLY-3913
> URL: https://issues.jboss.org/browse/WFLY-3913
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final
> Reporter: Jose Monreal
> Assignee: Tomaz Cerar
> Labels: https, standalone
> Fix For: 8.2.0.CR1, 9.0.0.CR1
>
> Attachments: standalone.xml
>
>
> When removing HTTPS socket-binding from the standalone.xml file, the server start's in errors.
> The errors are the following:
> {noformat}
> 13:55:32,002 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("http-listener" => "default")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]}
> 13:55:32,005 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.ws.config"],
> "Services that may be the cause:" => [
> "jboss.binding.https",
> "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
> ]
> }}
> 13:55:32,007 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "ejb3"),
> ("service" => "remote")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]}
> 13:55:32,074 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.binding.https (missing) dependents: [service jboss.undertow.listener.default]
> service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector]
>
> 13:55:32,085 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.1.0.Final "Kenny" started (with errors) in 3475ms - Started 197 of 252 services (3 services failed or missing dependencies, 78 services are lazy, passive or on-demand
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (WFLY-3913) HTTPS socket-binding definition always needed
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3913?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-3913:
-----------------------------------
not all your problems are caused by missing https socket-binding but problem exists in any case.
I will send PR to fix this in mean time, add https binding back and fix the remoting configuration as your configuration is in between http-remoting and remoting.
> HTTPS socket-binding definition always needed
> ---------------------------------------------
>
> Key: WFLY-3913
> URL: https://issues.jboss.org/browse/WFLY-3913
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final
> Reporter: Jose Monreal
> Assignee: Tomaz Cerar
> Labels: https, standalone
> Fix For: 8.2.0.CR1, 9.0.0.CR1
>
> Attachments: standalone.xml
>
>
> When removing HTTPS socket-binding from the standalone.xml file, the server start's in errors.
> The errors are the following:
> {noformat}
> 13:55:32,002 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("http-listener" => "default")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]}
> 13:55:32,005 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.ws.config"],
> "Services that may be the cause:" => [
> "jboss.binding.https",
> "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
> ]
> }}
> 13:55:32,007 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "ejb3"),
> ("service" => "remote")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]}
> 13:55:32,074 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.binding.https (missing) dependents: [service jboss.undertow.listener.default]
> service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector]
>
> 13:55:32,085 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.1.0.Final "Kenny" started (with errors) in 3475ms - Started 197 of 252 services (3 services failed or missing dependencies, 78 services are lazy, passive or on-demand
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (DROOLS-616) Move methods to access kjar resources from Internal-API to public-API
by Matteo Mortari (JIRA)
Matteo Mortari created DROOLS-616:
-------------------------------------
Summary: Move methods to access kjar resources from Internal-API to public-API
Key: DROOLS-616
URL: https://issues.jboss.org/browse/DROOLS-616
Project: Drools
Issue Type: Feature Request
Affects Versions: 6.1.0.Final
Reporter: Matteo Mortari
Assignee: Mark Proctor
Priority: Minor
Kindly consider to move methods to access kjar resources from Internal-API to public-API, in order to enable an appropriate way to load a file resource from a kjar "src/main/resources".
h5. Example scenario
Rule authors are placing additional files inside of src/main/resources, something along the lines of readme file, license file, and csv files for additional data parameters not needed by the rule themselves, but still required at runtime to be known by the "host" application.
At runtime the kjar is loaded via "KieContainer from KieRepository" so it's not directly available as a compile-scope maven dependency already inside my runtime-application, and to avoid methods involving manually ClassLoaders/getResource-on-class.
h5. Proposals:
Kindly consider moving at least the following methods:
- getFile() : File
- getFileNames() : Collection<String>
- getResource(String) : Resource
from InternalKieModule to public-API KieModule.
I leave to your expertise to evaluate which others may also be required, depending on the several options for deployments.
Thanks.
Ciao,
MM
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (WFLY-3913) HTTPS socket-binding definition always needed
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3913?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3913:
------------------------------
Fix Version/s: 8.2.0.CR1
9.0.0.CR1
> HTTPS socket-binding definition always needed
> ---------------------------------------------
>
> Key: WFLY-3913
> URL: https://issues.jboss.org/browse/WFLY-3913
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final
> Reporter: Jose Monreal
> Assignee: Tomaz Cerar
> Labels: https, standalone
> Fix For: 8.2.0.CR1, 9.0.0.CR1
>
> Attachments: standalone.xml
>
>
> When removing HTTPS socket-binding from the standalone.xml file, the server start's in errors.
> The errors are the following:
> {noformat}
> 13:55:32,002 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("http-listener" => "default")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]}
> 13:55:32,005 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.ws.config"],
> "Services that may be the cause:" => [
> "jboss.binding.https",
> "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
> ]
> }}
> 13:55:32,007 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "ejb3"),
> ("service" => "remote")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]}
> 13:55:32,074 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.binding.https (missing) dependents: [service jboss.undertow.listener.default]
> service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector]
>
> 13:55:32,085 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.1.0.Final "Kenny" started (with errors) in 3475ms - Started 197 of 252 services (3 services failed or missing dependencies, 78 services are lazy, passive or on-demand
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (WFLY-1067) Integrate JGroups with core AS security infrastructure
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-1067?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on WFLY-1067:
-------------------------------------------
That's very interesting. Thanks for pointing it out, Bela.
> Integrate JGroups with core AS security infrastructure
> ------------------------------------------------------
>
> Key: WFLY-1067
> URL: https://issues.jboss.org/browse/WFLY-1067
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering, Security
> Reporter: Brian Stansberry
> Assignee: Richard Achmatowicz
>
> Container task for better integrating JGroups security with overall AS security. The basic concept is the various security aware aspects of JGroups will expose an SPI, and the AS can create implementations of those SPIs that integrate with the AS security realms. The AS JGroups subsystem will inject the implementation into the JGroups runtime components.
> Subtasks are for the various aspects. These can be done separately but a common overall design should be created to ensure a consistent approach is taken.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (WFLY-3905) POJO JAX-WS endpoints should not be processed if packaged in EJB-jar
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3905?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFLY-3905:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1147657
> POJO JAX-WS endpoints should not be processed if packaged in EJB-jar
> --------------------------------------------------------------------
>
> Key: WFLY-3905
> URL: https://issues.jboss.org/browse/WFLY-3905
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 9.0.0.Alpha1
> Reporter: Kyle Lape
> Assignee: Kyle Lape
> Fix For: 9.0.0.Beta1
>
>
> If a POJO is defined like this in an EJB-jar:
> {code:java}
> package com.redhat.gss.ws;
> @javax.jws.WebService
> public class HelloService {
> public String sayHello() {
> return "Hello World!";
> }
> }
> {code}
> Deployment structure:
> {noformat}
> klape@localhost ws-java.jar$ tree
> .
> ├── com
> │ └── redhat
> │ └── gss
> │ └── ws
> │ └── HelloService.java
> └── META-INF
> └── MANIFEST.MF
> 5 directories, 2 files
> klape@localhost ws-java.jar$
> {noformat}
> Upon deployment, you get this in the log:
> {noformat}
> 16:52:51,372 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-7) JBWS024061: Adding service endpoint metadata: id=com.redhat.gss.ws.HelloService
> address=http://localhost:8080/ws-java/HelloService
> implementor=com.redhat.gss.ws.HelloService
> serviceName={http://ws.gss.redhat.com/}HelloServiceService
> portName={http://ws.gss.redhat.com/}HelloServicePort
> annotationWsdlLocation=null
> wsdlLocationOverride=null
> mtomEnabled=false
> 16:52:51,571 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-7) Creating Service {http://ws.gss.redhat.com/}HelloServiceService from class com.redhat.gss.ws.HelloService
> 16:52:51,879 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-7) Setting the server's publish address to be http://localhost:8080/ws-java/HelloService
> 16:52:51,925 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-7) JBWS024074: WSDL published to: file:/home/remote/klape/work/archives/wildfly-8.1.0.Final/standalone/data/wsdl/ws-java.jar/HelloServiceService.wsdl
> {noformat}
> Yet when you try to get the WSDL at {{http://localhost:8080/ws-java/HelloService?wsdl}} (pulled from the metadata in the log), you get a 404 error.
> JBossWS should not be trying to deploy the POJO endpoint from within an EJB-jar.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (WFLY-3913) HTTPS socket-binding definition always needed
by Jose Monreal (JIRA)
[ https://issues.jboss.org/browse/WFLY-3913?page=com.atlassian.jira.plugin.... ]
Jose Monreal updated WFLY-3913:
-------------------------------
Attachment: standalone.xml
standalone.xml to replicate problem
> HTTPS socket-binding definition always needed
> ---------------------------------------------
>
> Key: WFLY-3913
> URL: https://issues.jboss.org/browse/WFLY-3913
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final
> Reporter: Jose Monreal
> Assignee: Tomaz Cerar
> Labels: https, standalone
> Attachments: standalone.xml
>
>
> When removing HTTPS socket-binding from the standalone.xml file, the server start's in errors.
> The errors are the following:
> {noformat}
> 13:55:32,002 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("http-listener" => "default")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]}
> 13:55:32,005 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.ws.config"],
> "Services that may be the cause:" => [
> "jboss.binding.https",
> "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
> ]
> }}
> 13:55:32,007 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "ejb3"),
> ("service" => "remote")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]}
> 13:55:32,074 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.binding.https (missing) dependents: [service jboss.undertow.listener.default]
> service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector]
>
> 13:55:32,085 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.1.0.Final "Kenny" started (with errors) in 3475ms - Started 197 of 252 services (3 services failed or missing dependencies, 78 services are lazy, passive or on-demand
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (WFLY-3913) HTTPS socket-binding definition always needed
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3913?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-3913:
-----------------------------------
please upload whole file as attachment.
> HTTPS socket-binding definition always needed
> ---------------------------------------------
>
> Key: WFLY-3913
> URL: https://issues.jboss.org/browse/WFLY-3913
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final
> Reporter: Jose Monreal
> Assignee: Tomaz Cerar
> Labels: https, standalone
>
> When removing HTTPS socket-binding from the standalone.xml file, the server start's in errors.
> The errors are the following:
> {noformat}
> 13:55:32,002 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("http-listener" => "default")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]}
> 13:55:32,005 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.ws.config"],
> "Services that may be the cause:" => [
> "jboss.binding.https",
> "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
> ]
> }}
> 13:55:32,007 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "ejb3"),
> ("service" => "remote")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]}
> 13:55:32,074 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.binding.https (missing) dependents: [service jboss.undertow.listener.default]
> service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector]
>
> 13:55:32,085 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.1.0.Final "Kenny" started (with errors) in 3475ms - Started 197 of 252 services (3 services failed or missing dependencies, 78 services are lazy, passive or on-demand
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months