[
https://issues.jboss.org/browse/WFLY-1914?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-1914:
----------------------------------------
Carlo:
The subsystem was written such that the parsers treat
{code}
<subsystem xmlns="urn:jboss:domain:naming:1.0"/>
{code}
as equivalent to
{code}
<subsystem xmlns="urn:jboss:domain:naming:2.0">
<remote-naming/>
</subsystem>
{code}
The latter requires the remoting subsystem which is not present in appclient.xml.
We can't change the parser for 1.0 without breaking existing working configs.
Application client container doesn't start
------------------------------------------
Key: WFLY-1914
URL:
https://issues.jboss.org/browse/WFLY-1914
Project: WildFly
Issue Type: Bug
Components: Application Client
Affects Versions: 8.0.0.Alpha4
Reporter: jaikiran pai
Assignee: jaikiran pai
Application client container fails to start with the following exception:
{code}
16:23:40,742 INFO [org.jboss.as.jacorb] (MSC service thread 1-7) JBAS016328: CORBA
Naming Service started
16:23:40,744 ERROR [org.jboss.as.controller.management-operation] (Controller Boot
Thread) JBAS014613: Operation ("add") failed - address: ([
("subsystem" => "naming"),
("service" => "remote-naming")
]) - failure description: {"JBAS014771: Services with missing/unavailable
dependencies" => ["jboss.naming.remote is missing
[jboss.remoting.endpoint.subsystem]"]}
16:23:40,779 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service
status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.remoting.endpoint.subsystem (missing) dependents: [service
jboss.naming.remote]
16:23:40,782 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly
8.0.0.Beta1-SNAPSHOT "WildFly" started (with errors) in 1471ms - Started 99 of
103 services (1 services failed or missing dependencies, 9 services are lazy, passive or
on-demand)
{code}
when started using the following command:
{code}
JBOSS_HOME/bin/appclient.sh /foo/bar/some.jar
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira