[JBoss JIRA] (WFLY-10300) Mark deployment subsystem resources as runtime-only
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10300?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-10300:
------------------------------------
Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/11157)
> Mark deployment subsystem resources as runtime-only
> ---------------------------------------------------
>
> Key: WFLY-10300
> URL: https://issues.jboss.org/browse/WFLY-10300
> Project: WildFly
> Issue Type: Task
> Components: Management
> Reporter: Brian Stansberry
> Fix For: 13.0.0.Beta1
>
>
> Any /deployment=*/subsystem=xyx resource should be declared as runtime only.
> The integration suite should include a check of this, at least for the standalone server profiles where we create non-admin-only servers.
> Part of this task should be verifying that the setFeature(false) changes for WFLY-10299 are no longer needed once this is corrected, and if so removing them. (If they are still needed then why needs investigation.)
> Note that WFCORE-3432 eliminates the need to add setRuntimeOnly to children of /deployment=*/subsystem=xyx as it automatically ensures that a runtime-only parent only has runtime-only children.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-10300) Mark deployment subsystem resources as runtime-only
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10300?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFLY-10300:
---------------------------------------
Assignee: (was: Brian Stansberry)
> Mark deployment subsystem resources as runtime-only
> ---------------------------------------------------
>
> Key: WFLY-10300
> URL: https://issues.jboss.org/browse/WFLY-10300
> Project: WildFly
> Issue Type: Task
> Components: Management
> Reporter: Alexey Loubyansky
> Fix For: 13.0.0.Beta1
>
>
> Any /deployment=*/subsystem=xyx resource should be declared as runtime only.
> The integration suite should include a check of this, at least for the standalone server profiles where we create non-admin-only servers.
> Part of this task should be verifying that the setFeature(false) changes for WFLY-10299 are no longer needed once this is corrected, and if so removing them. (If they are still needed then why needs investigation.)
> Note that WFCORE-3432 eliminates the need to add setRuntimeOnly to children of /deployment=*/subsystem=xyx as it automatically ensures that a runtime-only parent only has runtime-only children.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-10300) Mark deployment subsystem resources as runtime-only
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10300?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-10300:
------------------------------------
Reporter: Brian Stansberry (was: Alexey Loubyansky)
> Mark deployment subsystem resources as runtime-only
> ---------------------------------------------------
>
> Key: WFLY-10300
> URL: https://issues.jboss.org/browse/WFLY-10300
> Project: WildFly
> Issue Type: Task
> Components: Management
> Reporter: Brian Stansberry
> Fix For: 13.0.0.Beta1
>
>
> Any /deployment=*/subsystem=xyx resource should be declared as runtime only.
> The integration suite should include a check of this, at least for the standalone server profiles where we create non-admin-only servers.
> Part of this task should be verifying that the setFeature(false) changes for WFLY-10299 are no longer needed once this is corrected, and if so removing them. (If they are still needed then why needs investigation.)
> Note that WFCORE-3432 eliminates the need to add setRuntimeOnly to children of /deployment=*/subsystem=xyx as it automatically ensures that a runtime-only parent only has runtime-only children.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-10300) Mark deployment subsystem resources as runtime-only
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10300?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-10300:
------------------------------------
Description:
Any /deployment=*/subsystem=xyx resource should be declared as runtime only.
The integration suite should include a check of this, at least for the standalone server profiles where we create non-admin-only servers.
Part of this task should be verifying that the setFeature(false) changes for WFLY-10299 are no longer needed once this is corrected, and if so removing them. (If they are still needed then why needs investigation.)
Note that WFCORE-3432 eliminates the need to add setRuntimeOnly to children of /deployment=*/subsystem=xyx as it automatically ensures that a runtime-only parent only has runtime-only children.
was:Feature specs should not be generated for deployments and subdeployments.
> Mark deployment subsystem resources as runtime-only
> ---------------------------------------------------
>
> Key: WFLY-10300
> URL: https://issues.jboss.org/browse/WFLY-10300
> Project: WildFly
> Issue Type: Task
> Components: Management
> Reporter: Alexey Loubyansky
> Assignee: Brian Stansberry
> Fix For: 13.0.0.Beta1
>
>
> Any /deployment=*/subsystem=xyx resource should be declared as runtime only.
> The integration suite should include a check of this, at least for the standalone server profiles where we create non-admin-only servers.
> Part of this task should be verifying that the setFeature(false) changes for WFLY-10299 are no longer needed once this is corrected, and if so removing them. (If they are still needed then why needs investigation.)
> Note that WFCORE-3432 eliminates the need to add setRuntimeOnly to children of /deployment=*/subsystem=xyx as it automatically ensures that a runtime-only parent only has runtime-only children.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-3766) Improve error message if a parent profile references a child profile's value
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3766?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-3766:
------------------------------------------
The weakness is this:
{code}
Possible registration points for this capability:
/profile=*/subsystem=jgroups
{code}
That can be misinterpreted as meaning any old profile will do. But actually only certain profiles will suffice. Listing those in some way would be good.
This needs thorough discussion before any work should begin; the above does not capture subtle points about how capability resolution works and what data is available. Not discussing first is likely to lead to unacceptable solutions.
> Improve error message if a parent profile references a child profile's value
> ----------------------------------------------------------------------------
>
> Key: WFCORE-3766
> URL: https://issues.jboss.org/browse/WFCORE-3766
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Management
> Affects Versions: 4.0.0.Final, 5.0.0.Alpha3, 3.1.0.Final
> Reporter: Brad Maxwell
> Labels: domain-mode
>
> EAP 7.1 CP1 boot up fails with the following error message when a profile extension is used
> {code:java}
> 14:13:39,201 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=infinispan/cache-container=hibernate/transport=jgroups' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller]
> 14:13:39,202 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=messaging-activemq/server=default/broadcast-group=bg-group1' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller]
> 14:13:39,202 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=infinispan/cache-container=web/transport=jgroups' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller]
> 14:13:39,202 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=messaging-activemq/server=default/discovery-group=dg-group1' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller]
> 14:13:39,203 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=infinispan/cache-container=server/transport=jgroups' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller]
> 14:13:39,203 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=infinispan/cache-container=ejb/transport=jgroups' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller]
> 14:13:39,215 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. [Host Controller]
> 14:13:39,217 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0178: Aborting with exit code 99 [Host Controller]
> 14:13:39,265 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0050: JBoss EAP 7.1.1.GA (WildFly Core 3.0.12.Final-redhat-1) stopped in 26ms [Host Controller]
> 14:13:39,611 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) WFLYPC0011: Process 'Host Controller' finished with an exit status of 99
> 14:13:39,613 INFO [org.jboss.as.process] (Thread-8) WFLYPC0017: Shutting down process controller 14:13:39,613 INFO [org.jboss.as.process] (Thread-8) WFLYPC0016: All processes finished; exiting
> {code}
> Can this error be improved to better direct the user to the issue?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-3766) Improve error message if a parent profile references a child profile's value
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3766?page=com.atlassian.jira.plugi... ]
Brian Stansberry moved JBEAP-14682 to WFCORE-3766:
--------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-3766 (was: JBEAP-14682)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Management
(was: Management)
Affects Version/s: 3.1.0.Final
5.0.0.Alpha3
4.0.0.Final
(was: 7.1.2.GA)
> Improve error message if a parent profile references a child profile's value
> ----------------------------------------------------------------------------
>
> Key: WFCORE-3766
> URL: https://issues.jboss.org/browse/WFCORE-3766
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Management
> Affects Versions: 3.1.0.Final, 5.0.0.Alpha3, 4.0.0.Final
> Reporter: Brad Maxwell
> Labels: domain-mode
>
> EAP 7.1 CP1 boot up fails with the following error message when a profile extension is used
> {code:java}
> 14:13:39,201 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=infinispan/cache-container=hibernate/transport=jgroups' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller]
> 14:13:39,202 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=messaging-activemq/server=default/broadcast-group=bg-group1' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller]
> 14:13:39,202 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=infinispan/cache-container=web/transport=jgroups' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller]
> 14:13:39,202 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=messaging-activemq/server=default/discovery-group=dg-group1' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller]
> 14:13:39,203 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=infinispan/cache-container=server/transport=jgroups' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller]
> 14:13:39,203 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=infinispan/cache-container=ejb/transport=jgroups' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller]
> 14:13:39,215 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. [Host Controller]
> 14:13:39,217 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0178: Aborting with exit code 99 [Host Controller]
> 14:13:39,265 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0050: JBoss EAP 7.1.1.GA (WildFly Core 3.0.12.Final-redhat-1) stopped in 26ms [Host Controller]
> 14:13:39,611 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) WFLYPC0011: Process 'Host Controller' finished with an exit status of 99
> 14:13:39,613 INFO [org.jboss.as.process] (Thread-8) WFLYPC0017: Shutting down process controller 14:13:39,613 INFO [org.jboss.as.process] (Thread-8) WFLYPC0016: All processes finished; exiting
> {code}
> Can this error be improved to better direct the user to the issue?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months