[JBoss JIRA] (WFCORE-5053) Prometheus JMX exporter jar, stops starting the wildfly server.
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-5053?page=com.atlassian.jira.plug... ]
James Perkins updated WFCORE-5053:
----------------------------------
Fix Version/s: 13.0.0.Beta1
> Prometheus JMX exporter jar, stops starting the wildfly server.
> ----------------------------------------------------------------
>
> Key: WFCORE-5053
> URL: https://issues.redhat.com/browse/WFCORE-5053
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Rakesh Kumar Shah
> Assignee: James Perkins
> Priority: Major
> Fix For: 13.0.0.Beta1
>
>
> Trying to integrate the Prometheus JMX exporter with wildfly. After spending lot of time and work around it, wildfly is not starting. It throws following exception.
> {code}
> java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager
> at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
> at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at java.logging/java.util.logging.LogManager$1.run(LogManager.java:239)
> at java.logging/java.util.logging.LogManager$1.run(LogManager.java:223)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at java.logging/java.util.logging.LogManager.<clinit>(LogManager.java:223)
> at java.logging/java.util.logging.Logger.demandLogger(Logger.java:648)
> at java.logging/java.util.logging.Logger.getLogger(Logger.java:717)
> at java.logging/java.util.logging.Logger.getLogger(Logger.java:701)
> at io.prometheus.jmx.shaded.io.prometheus.jmx.JmxCollector.<clinit>(JmxCollector.java:39)
> at io.prometheus.jmx.shaded.io.prometheus.jmx.JavaAgent.premain(JavaAgent.java:29)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513)
> at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525)
> WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
> at java.base/java.lang.Class.forName0(Native Method)
> at java.base/java.lang.Class.forName(Class.java:398)
> at org.jboss.modules.Module.run(Module.java:340)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:617)
> Caused by: java.lang.ClassNotFoundException: org.jboss.logmanager.Level
> at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
> at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at org.jboss.modules.JDKSpecific.getSystemClass(JDKSpecific.java:183)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:395)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFCORE-5053) Prometheus JMX exporter jar, stops starting the wildfly server.
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-5053?page=com.atlassian.jira.plug... ]
James Perkins resolved WFCORE-5053.
-----------------------------------
Resolution: Done
> Prometheus JMX exporter jar, stops starting the wildfly server.
> ----------------------------------------------------------------
>
> Key: WFCORE-5053
> URL: https://issues.redhat.com/browse/WFCORE-5053
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Rakesh Kumar Shah
> Assignee: James Perkins
> Priority: Major
> Fix For: 13.0.0.Beta1
>
>
> Trying to integrate the Prometheus JMX exporter with wildfly. After spending lot of time and work around it, wildfly is not starting. It throws following exception.
> {code}
> java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager
> at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
> at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at java.logging/java.util.logging.LogManager$1.run(LogManager.java:239)
> at java.logging/java.util.logging.LogManager$1.run(LogManager.java:223)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at java.logging/java.util.logging.LogManager.<clinit>(LogManager.java:223)
> at java.logging/java.util.logging.Logger.demandLogger(Logger.java:648)
> at java.logging/java.util.logging.Logger.getLogger(Logger.java:717)
> at java.logging/java.util.logging.Logger.getLogger(Logger.java:701)
> at io.prometheus.jmx.shaded.io.prometheus.jmx.JmxCollector.<clinit>(JmxCollector.java:39)
> at io.prometheus.jmx.shaded.io.prometheus.jmx.JavaAgent.premain(JavaAgent.java:29)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513)
> at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525)
> WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
> at java.base/java.lang.Class.forName0(Native Method)
> at java.base/java.lang.Class.forName(Class.java:398)
> at org.jboss.modules.Module.run(Module.java:340)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:617)
> Caused by: java.lang.ClassNotFoundException: org.jboss.logmanager.Level
> at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
> at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at org.jboss.modules.JDKSpecific.getSystemClass(JDKSpecific.java:183)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:395)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFCORE-5053) Prometheus JMX exporter jar, stops starting the wildfly server.
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-5053?page=com.atlassian.jira.plug... ]
James Perkins commented on WFCORE-5053:
---------------------------------------
[~rakesh.shah1977] There is a workaround that will be introduced in WildFly 21. See WFCORE-4748 for the details there. Essentially though you'd just need to update the {{standalone.conf.bat}} with something like the following.
{code}
set "MODULE_OPTS=-javaagent:%JBOSS_HOME%\jmx_prometheus_javaagent-0.13.0.jar=9080:%JBOSS_HOME%\standalone\configuration\config.yaml
{code}
> Prometheus JMX exporter jar, stops starting the wildfly server.
> ----------------------------------------------------------------
>
> Key: WFCORE-5053
> URL: https://issues.redhat.com/browse/WFCORE-5053
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Rakesh Kumar Shah
> Assignee: James Perkins
> Priority: Major
>
> Trying to integrate the Prometheus JMX exporter with wildfly. After spending lot of time and work around it, wildfly is not starting. It throws following exception.
> {code}
> java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager
> at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
> at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at java.logging/java.util.logging.LogManager$1.run(LogManager.java:239)
> at java.logging/java.util.logging.LogManager$1.run(LogManager.java:223)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at java.logging/java.util.logging.LogManager.<clinit>(LogManager.java:223)
> at java.logging/java.util.logging.Logger.demandLogger(Logger.java:648)
> at java.logging/java.util.logging.Logger.getLogger(Logger.java:717)
> at java.logging/java.util.logging.Logger.getLogger(Logger.java:701)
> at io.prometheus.jmx.shaded.io.prometheus.jmx.JmxCollector.<clinit>(JmxCollector.java:39)
> at io.prometheus.jmx.shaded.io.prometheus.jmx.JavaAgent.premain(JavaAgent.java:29)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513)
> at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525)
> WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
> at java.base/java.lang.Class.forName0(Native Method)
> at java.base/java.lang.Class.forName(Class.java:398)
> at org.jboss.modules.Module.run(Module.java:340)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:617)
> Caused by: java.lang.ClassNotFoundException: org.jboss.logmanager.Level
> at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
> at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at org.jboss.modules.JDKSpecific.getSystemClass(JDKSpecific.java:183)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:395)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (DROOLS-5512) Unsaved changes dialog for a Test Scenario executed right after creation
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-5512?page=com.atlassian.jira.plug... ]
Yeser Amer reassigned DROOLS-5512:
----------------------------------
Assignee: Yeser Amer (was: Daniele Zonca)
> Unsaved changes dialog for a Test Scenario executed right after creation
> ------------------------------------------------------------------------
>
> Key: DROOLS-5512
> URL: https://issues.redhat.com/browse/DROOLS-5512
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.41.0.Final
> Reporter: Jan Stastny
> Assignee: Yeser Amer
> Priority: Major
>
> There is once again an Unsaved Changes dialog presented to user even though no changes has been made.
> This time it is when user creates Test Scenario, fills in facts and values, saves and executes the test scenario right away. When clicking save and trying to close again it does not appear again. There us not commit in niogit connected with the second save.
> When user closes and reopens editor between save and run, all works fine.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFCORE-3766) Improve error message if a parent profile references a child profile's value
by Brad Maxwell (Jira)
[ https://issues.redhat.com/browse/WFCORE-3766?page=com.atlassian.jira.plug... ]
Brad Maxwell edited comment on WFCORE-3766 at 7/16/20 11:51 AM:
----------------------------------------------------------------
[~mshikalw] 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}
I ran the example with CD20 and the error has improved , it no longer says temp
{code:java}
[Host Controller] 10:48:45,897 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=base-full-ha/subsystem=messaging-activemq/server=default/jgroups-broadcast-group=bg-group1' are not available:
[Host Controller] org.wildfly.clustering.default-command-dispatcher-factory in context 'profile=base-full-ha'; Possible registration points for this capability:
[Host Controller] /profile=*/subsystem=infinispan
[Host Controller] /profile=*/subsystem=jgroups
[Host Controller] 10:48:45,897 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=base-full-ha/subsystem=messaging-activemq/server=default/jgroups-discovery-group=dg-group1' are not available:
[Host Controller] org.wildfly.clustering.default-command-dispatcher-factory in context 'profile=base-full-ha'; Possible registration points for this capability:
[Host Controller] /profile=*/subsystem=infinispan
[Host Controller] /profile=*/subsystem=jgroups
[Host Controller] 10:48:45,898 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=base-full-ha/subsystem=singleton/singleton-policy=default' are not available:
[Host Controller] org.wildfly.clustering.cache.default-singleton-service-configurator-factory.server in context 'profile=base-full-ha'; Possible registration points for this capability:
[Host Controller] /profile=*/subsystem=infinispan/cache-container=* {code}
was (Author: bmaxwell):
[~mshikalw] 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}
I ran the example with CD20 and the error has improved , it no longer says temp
{code:java}
[Host Controller] 10:48:45,897 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=base-full-ha/subsystem=messaging-activemq/server=default/jgroups-broadcast-group=bg-group1' are not available:
[Host Controller] org.wildfly.clustering.default-command-dispatcher-factory in context 'profile=base-full-ha'; Possible registration points for this capability:
[Host Controller] /profile=*/subsystem=infinispan
[Host Controller] /profile=*/subsystem=jgroups
[Host Controller] 10:48:45,897 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=base-full-ha/subsystem=messaging-activemq/server=default/jgroups-discovery-group=dg-group1' are not available:
[Host Controller] org.wildfly.clustering.default-command-dispatcher-factory in context 'profile=base-full-ha'; Possible registration points for this capability:
[Host Controller] /profile=*/subsystem=infinispan
[Host Controller] /profile=*/subsystem=jgroups
[Host Controller] 10:48:45,898 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=base-full-ha/subsystem=singleton/singleton-policy=default' are not available:
[Host Controller] org.wildfly.clustering.cache.default-singleton-service-configurator-factory.server in context 'profile=base-full-ha'; Possible registration points for this capability:
[Host Controller] /profile=*/subsystem=infinispan/cache-container=* {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.
> 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)
5 years, 10 months
[JBoss JIRA] (WFCORE-3766) Improve error message if a parent profile references a child profile's value
by Brad Maxwell (Jira)
[ https://issues.redhat.com/browse/WFCORE-3766?page=com.atlassian.jira.plug... ]
Brad Maxwell edited comment on WFCORE-3766 at 7/16/20 11:50 AM:
----------------------------------------------------------------
[~mshikalw] 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}
I ran the example with CD20 and the error has improved , it no longer says temp
{code:java}
[Host Controller] 10:48:45,897 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=base-full-ha/subsystem=messaging-activemq/server=default/jgroups-broadcast-group=bg-group1' are not available:
[Host Controller] org.wildfly.clustering.default-command-dispatcher-factory in context 'profile=base-full-ha'; Possible registration points for this capability:
[Host Controller] /profile=*/subsystem=infinispan
[Host Controller] /profile=*/subsystem=jgroups
[Host Controller] 10:48:45,897 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=base-full-ha/subsystem=messaging-activemq/server=default/jgroups-discovery-group=dg-group1' are not available:
[Host Controller] org.wildfly.clustering.default-command-dispatcher-factory in context 'profile=base-full-ha'; Possible registration points for this capability:
[Host Controller] /profile=*/subsystem=infinispan
[Host Controller] /profile=*/subsystem=jgroups
[Host Controller] 10:48:45,898 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=base-full-ha/subsystem=singleton/singleton-policy=default' are not available:
[Host Controller] org.wildfly.clustering.cache.default-singleton-service-configurator-factory.server in context 'profile=base-full-ha'; Possible registration points for this capability:
[Host Controller] /profile=*/subsystem=infinispan/cache-container=* {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):
[~mshikalw] 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.
> 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)
5 years, 10 months
[JBoss JIRA] (WFCORE-3766) Improve error message if a parent profile references a child profile's value
by Brad Maxwell (Jira)
[ https://issues.redhat.com/browse/WFCORE-3766?page=com.atlassian.jira.plug... ]
Brad Maxwell edited comment on WFCORE-3766 at 7/16/20 11:44 AM:
----------------------------------------------------------------
[~mshikalw] 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}
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.
> 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)
5 years, 10 months
[JBoss JIRA] (DROOLS-5512) Unsaved changes dialog for a Test Scenario executed right after creation
by Jan Stastny (Jira)
Jan Stastny created DROOLS-5512:
-----------------------------------
Summary: Unsaved changes dialog for a Test Scenario executed right after creation
Key: DROOLS-5512
URL: https://issues.redhat.com/browse/DROOLS-5512
Project: Drools
Issue Type: Bug
Components: Scenario Simulation and Testing
Affects Versions: 7.41.0.Final
Reporter: Jan Stastny
Assignee: Daniele Zonca
There is once again an Unsaved Changes dialog presented to user even though no changes has been made.
This time it is when user creates Test Scenario, fills in facts and values, saves and executes the test scenario right away. When clicking save and trying to close again it does not appear again. There us not commit in niogit connected with the second save.
When user closes and reopens editor between save and run, all works fine.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFCORE-3766) Improve error message if a parent profile references a child profile's value
by Brad Maxwell (Jira)
[ https://issues.redhat.com/browse/WFCORE-3766?page=com.atlassian.jira.plug... ]
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)
5 years, 10 months
[JBoss JIRA] (WFCORE-3766) Improve error message if a parent profile references a child profile's value
by Brad Maxwell (Jira)
[ https://issues.redhat.com/browse/WFCORE-3766?page=com.atlassian.jira.plug... ]
Brad Maxwell commented on WFCORE-3766:
--------------------------------------
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)
5 years, 10 months