[jboss-jira] [JBoss JIRA] (WFCORE-3766) Improve error message if a parent profile references a child profile's value

Brad Maxwell (Jira) issues at jboss.org
Thu Jul 16 11:45:00 EDT 2020


    [ https://issues.redhat.com/browse/WFCORE-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248919#comment-14248919 ] 

Brad Maxwell edited comment on WFCORE-3766 at 7/16/20 11:44 AM:
----------------------------------------------------------------

 
 The reason this particular example fails is the profile used is full-ha which defines the jgroups / infinispan subsystem, the base-full-ha defines the messaging subsystem which needs jgroups / infinispan which is not defined in that profile.  So one fix for this config is to copy the jgroups / infinispan subsystem into the base-full-ha profile.

So the enhancement is to see if we can better indicate to the user what the issue is.
{code:java}
     <profile name="full-ha" includes="base-full-ha">
            <subsystem xmlns="urn:jboss:domain:jgroups:7.0">
            <subsystem xmlns="urn:jboss:domain:infinispan:9.0">
        <profile name="base-full-ha">
            <subsystem xmlns="urn:jboss:domain:messaging-activemq:8.0">{code}
 

So this error :
{code:java}
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]
  {code}
Says temp-full-ha/subsystem=infinispan/cache-container=hibernate/transport=jgroups is not available
 * From the user's perspective there is no temp-full-ha , it is full-ha.  
 * the current error suggests jgroups is not available for infinispan, but jgroups and infinispan are both defined in full-ha , the real issue is messaging in base-full-ha needs jgroups, so the message is misleading.


was (Author: bmaxwell):
 
The reason this particular example fails is the profile used is full-ha which defines the jgroups / infinispan subsystem, the base-full-ha defines the messaging subsystem which needs jgroups / infinispan which is not defined in that profile.  So one fix for this config is to copy the jgroups / infinispan subsystem into the base-full-ha profile.

So the enhancement is to see if we can better indicate to the user what the issue is.
{code:java}
     <profile name="full-ha" includes="base-full-ha">
            <subsystem xmlns="urn:jboss:domain:jgroups:7.0">
            <subsystem xmlns="urn:jboss:domain:infinispan:9.0">
        <profile name="base-full-ha">
            <subsystem xmlns="urn:jboss:domain:messaging-activemq:8.0">{code}
{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]  {code}
 
 * [|https://issues.redhat.com/secure/AddComment!default.jspa?id=12747093]

> Improve error message if a parent profile references a child profile's value
> ----------------------------------------------------------------------------
>
>                 Key: WFCORE-3766
>                 URL: https://issues.redhat.com/browse/WFCORE-3766
>             Project: WildFly Core
>          Issue Type: Enhancement
>          Components: Management
>    Affects Versions: 3.1.0.Final, 4.0.0.Final, 5.0.0.Alpha3
>            Reporter: Brad Maxwell
>            Assignee: Moulali Shikalwadi
>            Priority: Major
>              Labels: domain-mode
>         Attachments: WFCORE-3766-config.zip
>
>
> 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.13.8#713008)



More information about the jboss-jira mailing list