[
https://issues.jboss.org/browse/WFCORE-955?page=com.atlassian.jira.plugin...
]
Kabir Khan commented on WFCORE-955:
-----------------------------------
[~brian.stansberry] Take
https://github.com/wildfly/wildfly-core/compare/wildfly:master...kabir:WF...
as my issue, and use the domain.xml above with all servers removed from host.xml.
The issue is that the undertow adds the capability
profile=default/org.wildfly.undertow.listener.default which depends on
org.wildfly.network.socket-binding.http, which is a ProfileChildCapabilityScope. n the
loop in CapabilityRegistry.resolveCapabilities() it calls findSatisfactoryCapability()
which returns a SatisfactoryCapability with a multipleCapabilities with size 1, and the
only entry is now a SocketBindingGroupChildScope. Since the
SatisfactoryCapability.multipleCapabilities != null it ends up calling
dependentContest.getIncludingScopes() (the dependentContext is of type
ProfileChildCapabilityScope), and so when it reaches storeIncludes() called with
key='new' it blows up since there is no 'nonsense' profile.
In core on its own this does not happen since there is no undertow causing this behaviour.
Server is not responding after attempt to set parent of profile to
non-existent profile
---------------------------------------------------------------------------------------
Key: WFCORE-955
URL:
https://issues.jboss.org/browse/WFCORE-955
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 2.0.0.Beta5
Reporter: Marek Kopecký
Assignee: Brian Stansberry
Priority: Critical
Fix For: 2.0.0.CR1
*Description of problem:*
Server is not responding after attempt to set parent of profile to non-existent profile.
Server is not responding also after attempt to set parent of socket-binding-group to
non-existent socket-binding-group.
This works correctly on wildfly-core (2.0.0.Beta4). But this occurs on wildfly (master
branch) and on EAP 7.0.0.DR9. It may be some integration issue.
Priority of this jira tends to be critical.
*How reproducible:*
Always
*Steps to Reproduce (profile):*
# Get fresh EAP
# ./domain.sh
# ./jboss-cli.sh
## /profile=new:add()
## /profile=new:write-attribute(name=includes,value=\[nonsence\])
## /profile=new:remove
*Actual results:*
{noformat}
[domain@localhost:9990 /] /profile=new:write-attribute(name=includes,value=[nonsence])
{
"outcome" => "failed",
"failure-description" =>
"java.lang.NullPointerException:null"
}
[domain@localhost:9990 /] /profile=new:remove
{noformat}
* server needs to be restarted
*Expected results:*
{noformat}
[domain@localhost:9990 /] /profile=new:write-attribute(name=includes,value=[nonsence])
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" =>
"WFLYCTL0369: Required capabilities are not available:
org.wildfly.domain.profile.nonsence in context 'profiles'"},
"rolled-back" => true
}
[domain@localhost:9990 /] /profile=new:remove
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined
}
{noformat}
*Steps to reproduce (socket-binding-group):*
# Get fresh EAP
# ./domain.sh
# ./jboss-cli.sh
## /profile=new:add()
## /socket-binding-group=testt:add(default-interface=public,includes=\[nonsence\])
## /profile=new:remove
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)