[JBoss JIRA] (WFLY-11127) Can not get activemq and undertow subsystem data from HTTP management api
by Toni Moreno (Jira)
[ https://issues.jboss.org/browse/WFLY-11127?page=com.atlassian.jira.plugin... ]
Toni Moreno updated WFLY-11127:
-------------------------------
Description:
As described in https://github.com/wildfly/wildfly/issues/11309
I can not get some subsystems info data with the HTTP management API working with
{{ "product-version" => "12.0.0.Final",
"product-community-identifier" => "Product",
"product-home" => "/usr/local/wildfly-12.0.0.Final",
"standalone-or-domain-identifier" => "HOST_CONTROLLER",
"host-operating-system" => "Debian GNU/Linux 8 (jessie)}}
This the a activemq POST request with curl and its error
{{root@snmpcoldev01:~# curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"host":"master","server":"server-two","subsystem":"messaging-activemq","server":"default"},"operation":"read-children-resources","child-type":"jms-queue","include-runtime":"true","json.pretty":1,"recursive-depth":2}' -u admin
Enter host password for user 'admin':
HTTP/1.1 401 Unauthorized
Connection: keep-alive
WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABCwnAAANoo77ka2vPx9H1LY0IuT5cmkcn5HWBS88gigGzT786K6qnnpMAk=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth
X-Frame-Options: SAMEORIGIN
Content-Length: 77
Content-Type: text/html
Date: Sat, 02 Jun 2018 08:05:53 GMT
HTTP/1.1 500 Internal Server Error
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
Content-Type: application/json; charset=utf-8
Content-Length: 103
Date: Sat, 02 Jun 2018 08:05:53 GMT
"java.io.IOException: org.jboss.dmr.stream.ModelException: Unexpected content following the DMR}}
And this the query with the GUI client
[jboss_jms_queue_gui_query|https://user-images.githubusercontent.com/58834...]
Also with undertow subsystem
{{root@snmpcoldev01:~# curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"address":{"host":"master","server":"server-two","subsystem":"undertow","server":"default-server","http-listener":"default"},"include-runtime":"true","json.pretty":1,"operation":"read-resource","recursive-depth":0}' -u admin
Enter host password for user 'admin':
HTTP/1.1 401 Unauthorized
Connection: keep-alive
WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABC0jwAAN04NaeQD9tlEeeNzizRu5PGuUY9Adi18uuLUzOM1RZNHWkCqnc4=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth
X-Frame-Options: SAMEORIGIN
Content-Length: 77
Content-Type: text/html
Date: Sat, 02 Jun 2018 08:19:54 GMT
HTTP/1.1 500 Internal Server Error
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
Content-Type: application/json; charset=utf-8
Content-Length: 302
Date: Sat, 02 Jun 2018 08:19:54 GMT
{
"outcome" : "failed",
"failure-description" : "WFLYCTL0030: No resource definition is registered for address [\n (\"host\" => \"master\"),\n (\"server\" => \"default-server\"),\n (\"subsystem\" => \"undertow\"),\n (\"http-listener\" => \"default\")\n]",
"rolled-back" : true
}}}
Here Image of the GUI management query.
[jboss_undertow_listener_gui_query|https://user-images.githubusercontent.c...]
was:
As described in https://github.com/wildfly/wildfly/issues/11309
I can not get some subsystems info data with the HTTP management API working with
````
"product-version" => "12.0.0.Final",
"product-community-identifier" => "Product",
"product-home" => "/usr/local/wildfly-12.0.0.Final",
"standalone-or-domain-identifier" => "HOST_CONTROLLER",
"host-operating-system" => "Debian GNU/Linux 8 (jessie)
````
This the a activemq POST request with curl and its error
````
root@snmpcoldev01:~# curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"host":"master","server":"server-two","subsystem":"messaging-activemq","server":"default"},"operation":"read-children-resources","child-type":"jms-queue","include-runtime":"true","json.pretty":1,"recursive-depth":2}' -u admin
Enter host password for user 'admin':
HTTP/1.1 401 Unauthorized
Connection: keep-alive
WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABCwnAAANoo77ka2vPx9H1LY0IuT5cmkcn5HWBS88gigGzT786K6qnnpMAk=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth
X-Frame-Options: SAMEORIGIN
Content-Length: 77
Content-Type: text/html
Date: Sat, 02 Jun 2018 08:05:53 GMT
HTTP/1.1 500 Internal Server Error
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
Content-Type: application/json; charset=utf-8
Content-Length: 103
Date: Sat, 02 Jun 2018 08:05:53 GMT
"java.io.IOException: org.jboss.dmr.stream.ModelException: Unexpected content following the DMR
````
And this the query with the GUI client
.
Also with undertow subsystem
````
root@snmpcoldev01:~# curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"address":{"host":"master","server":"server-two","subsystem":"undertow","server":"default-server","http-listener":"default"},"include-runtime":"true","json.pretty":1,"operation":"read-resource","recursive-depth":0}' -u admin
Enter host password for user 'admin':
HTTP/1.1 401 Unauthorized
Connection: keep-alive
WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABC0jwAAN04NaeQD9tlEeeNzizRu5PGuUY9Adi18uuLUzOM1RZNHWkCqnc4=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth
X-Frame-Options: SAMEORIGIN
Content-Length: 77
Content-Type: text/html
Date: Sat, 02 Jun 2018 08:19:54 GMT
HTTP/1.1 500 Internal Server Error
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
Content-Type: application/json; charset=utf-8
Content-Length: 302
Date: Sat, 02 Jun 2018 08:19:54 GMT
{
"outcome" : "failed",
"failure-description" : "WFLYCTL0030: No resource definition is registered for address [\n (\"host\" => \"master\"),\n (\"server\" => \"default-server\"),\n (\"subsystem\" => \"undertow\"),\n (\"http-listener\" => \"default\")\n]",
"rolled-back" : true
}
````
> Can not get activemq and undertow subsystem data from HTTP management api
> -------------------------------------------------------------------------
>
> Key: WFLY-11127
> URL: https://issues.jboss.org/browse/WFLY-11127
> Project: WildFly
> Issue Type: Bug
> Components: Management, Web (Undertow)
> Affects Versions: 12.0.0.Final
> Reporter: Toni Moreno
> Assignee: Jeff Mesnil
> Priority: Critical
>
> As described in https://github.com/wildfly/wildfly/issues/11309
> I can not get some subsystems info data with the HTTP management API working with
>
> {{ "product-version" => "12.0.0.Final",
> "product-community-identifier" => "Product",
> "product-home" => "/usr/local/wildfly-12.0.0.Final",
> "standalone-or-domain-identifier" => "HOST_CONTROLLER",
> "host-operating-system" => "Debian GNU/Linux 8 (jessie)}}
> This the a activemq POST request with curl and its error
> {{root@snmpcoldev01:~# curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"host":"master","server":"server-two","subsystem":"messaging-activemq","server":"default"},"operation":"read-children-resources","child-type":"jms-queue","include-runtime":"true","json.pretty":1,"recursive-depth":2}' -u admin
> Enter host password for user 'admin':
> HTTP/1.1 401 Unauthorized
> Connection: keep-alive
> WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABCwnAAANoo77ka2vPx9H1LY0IuT5cmkcn5HWBS88gigGzT786K6qnnpMAk=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth
> X-Frame-Options: SAMEORIGIN
> Content-Length: 77
> Content-Type: text/html
> Date: Sat, 02 Jun 2018 08:05:53 GMT
> HTTP/1.1 500 Internal Server Error
> Connection: keep-alive
> X-Frame-Options: SAMEORIGIN
> Content-Type: application/json; charset=utf-8
> Content-Length: 103
> Date: Sat, 02 Jun 2018 08:05:53 GMT
> "java.io.IOException: org.jboss.dmr.stream.ModelException: Unexpected content following the DMR}}
> And this the query with the GUI client
> [jboss_jms_queue_gui_query|https://user-images.githubusercontent.com/58834...]
> Also with undertow subsystem
> {{root@snmpcoldev01:~# curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"address":{"host":"master","server":"server-two","subsystem":"undertow","server":"default-server","http-listener":"default"},"include-runtime":"true","json.pretty":1,"operation":"read-resource","recursive-depth":0}' -u admin
> Enter host password for user 'admin':
> HTTP/1.1 401 Unauthorized
> Connection: keep-alive
> WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABC0jwAAN04NaeQD9tlEeeNzizRu5PGuUY9Adi18uuLUzOM1RZNHWkCqnc4=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth
> X-Frame-Options: SAMEORIGIN
> Content-Length: 77
> Content-Type: text/html
> Date: Sat, 02 Jun 2018 08:19:54 GMT
> HTTP/1.1 500 Internal Server Error
> Connection: keep-alive
> X-Frame-Options: SAMEORIGIN
> Content-Type: application/json; charset=utf-8
> Content-Length: 302
> Date: Sat, 02 Jun 2018 08:19:54 GMT
> {
> "outcome" : "failed",
> "failure-description" : "WFLYCTL0030: No resource definition is registered for address [\n (\"host\" => \"master\"),\n (\"server\" => \"default-server\"),\n (\"subsystem\" => \"undertow\"),\n (\"http-listener\" => \"default\")\n]",
> "rolled-back" : true
> }}}
> Here Image of the GUI management query.
> [jboss_undertow_listener_gui_query|https://user-images.githubusercontent.c...]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11127) Can not get activemq and undertow subsystem data from HTTP management api
by Toni Moreno (Jira)
Toni Moreno created WFLY-11127:
----------------------------------
Summary: Can not get activemq and undertow subsystem data from HTTP management api
Key: WFLY-11127
URL: https://issues.jboss.org/browse/WFLY-11127
Project: WildFly
Issue Type: Bug
Components: Management, Web (Undertow)
Affects Versions: 12.0.0.Final
Reporter: Toni Moreno
Assignee: Jeff Mesnil
As described in https://github.com/wildfly/wildfly/issues/11309
I can not get some subsystems info data with the HTTP management API working with
````
"product-version" => "12.0.0.Final",
"product-community-identifier" => "Product",
"product-home" => "/usr/local/wildfly-12.0.0.Final",
"standalone-or-domain-identifier" => "HOST_CONTROLLER",
"host-operating-system" => "Debian GNU/Linux 8 (jessie)
````
This the a activemq POST request with curl and its error
````
root@snmpcoldev01:~# curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"host":"master","server":"server-two","subsystem":"messaging-activemq","server":"default"},"operation":"read-children-resources","child-type":"jms-queue","include-runtime":"true","json.pretty":1,"recursive-depth":2}' -u admin
Enter host password for user 'admin':
HTTP/1.1 401 Unauthorized
Connection: keep-alive
WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABCwnAAANoo77ka2vPx9H1LY0IuT5cmkcn5HWBS88gigGzT786K6qnnpMAk=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth
X-Frame-Options: SAMEORIGIN
Content-Length: 77
Content-Type: text/html
Date: Sat, 02 Jun 2018 08:05:53 GMT
HTTP/1.1 500 Internal Server Error
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
Content-Type: application/json; charset=utf-8
Content-Length: 103
Date: Sat, 02 Jun 2018 08:05:53 GMT
"java.io.IOException: org.jboss.dmr.stream.ModelException: Unexpected content following the DMR
````
And this the query with the GUI client
.
Also with undertow subsystem
````
root@snmpcoldev01:~# curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"address":{"host":"master","server":"server-two","subsystem":"undertow","server":"default-server","http-listener":"default"},"include-runtime":"true","json.pretty":1,"operation":"read-resource","recursive-depth":0}' -u admin
Enter host password for user 'admin':
HTTP/1.1 401 Unauthorized
Connection: keep-alive
WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABC0jwAAN04NaeQD9tlEeeNzizRu5PGuUY9Adi18uuLUzOM1RZNHWkCqnc4=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth
X-Frame-Options: SAMEORIGIN
Content-Length: 77
Content-Type: text/html
Date: Sat, 02 Jun 2018 08:19:54 GMT
HTTP/1.1 500 Internal Server Error
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
Content-Type: application/json; charset=utf-8
Content-Length: 302
Date: Sat, 02 Jun 2018 08:19:54 GMT
{
"outcome" : "failed",
"failure-description" : "WFLYCTL0030: No resource definition is registered for address [\n (\"host\" => \"master\"),\n (\"server\" => \"default-server\"),\n (\"subsystem\" => \"undertow\"),\n (\"http-listener\" => \"default\")\n]",
"rolled-back" : true
}
````
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (JBLOGGING-111) LoggerProvider configured with new ServiceLoader crash
by Steven Sharp (Jira)
[ https://issues.jboss.org/browse/JBLOGGING-111?page=com.atlassian.jira.plu... ]
Steven Sharp commented on JBLOGGING-111:
----------------------------------------
[~jamezp], you mentioned that "The SPI is really meant to enable users to provide their own provider." To do this, you have to write your provider from scratch as all the abstract implementations are package private as well. The only documentation I could find for this feature, other than the code, was the [hibernate documentation|http://docs.jboss.org/hibernate/orm/current/topical/html_si...] which is incorrect. In the code, the exception ({{ServiceConfigurationError}}) is silently eaten leaving developers wondering why their logging implementation of choice doesn't work.
When we deploy our application, adding a system property is not possible. An ugly workaround is to create a delegate class in the org.jboss.logging package, but that is unmaintainable. The implementation classes should be public so the logging implementation can be chosen via the ServiceLoader. At least expose the result of the {{ServiceLoader.load()}} method so developers will know that it failed. Either this issue should be reopened or a new one should be created.
> LoggerProvider configured with new ServiceLoader crash
> ------------------------------------------------------
>
> Key: JBLOGGING-111
> URL: https://issues.jboss.org/browse/JBLOGGING-111
> Project: JBoss Logging
> Issue Type: Bug
> Affects Versions: 3.2.0.Beta1
> Environment: Weblogic 10.3.2.0
> Configured in ejb jar, deployed by an ear file
> Reporter: Frederic Allard
> Assignee: James Perkins
> Priority: Major
> Fix For: 3.2.0.Final
>
>
> There is a new feature in the beta which uses the ServiceLoader to specify a LoggerProvider to be used by JBoss Logging.
> org.jboss.logging.LoggerProviders snippet :
> {code}
> // Next try for a service provider
> try {
> final ServiceLoader<LoggerProvider> loader = ServiceLoader.load(LoggerProvider.class, cl);
> if (loader.iterator().hasNext()) {
> return loader.iterator().next();
> }
> } catch (Throwable ignore) {
> // TODO consider printing the stack trace as it should only happen once
> }
> {code}
> When you try to configure a provider (ex. org.jboss.logging.Slf4jLoggerProvider), the ServiceLoader crash silently and ignore the provider.
> {code}
> java.util.ServiceConfigurationError: org.jboss.logging.LoggerProvider: Provider org.jboss.logging.Slf4jLoggerProvider could not be instantiated: java.lang.IllegalAccessException: Class java.util.ServiceLoader$LazyIterator can not access a member of class org.jboss.logging.Slf4jLoggerProvider with modifiers ""
> at java.util.ServiceLoader.fail(ServiceLoader.java:207)
> at java.util.ServiceLoader.access$100(ServiceLoader.java:164)
> at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:353)
> at java.util.ServiceLoader$1.next(ServiceLoader.java:421)
> at org.jboss.logging.LoggerProviders.findProvider(LoggerProviders.java:70)
> at org.jboss.logging.LoggerProviders.find(LoggerProviders.java:32)
> at org.jboss.logging.LoggerProviders.<clinit>(LoggerProviders.java:29)
> at org.jboss.logging.Logger.getLogger(Logger.java:2177)
> at org.jboss.logging.Logger$1.run(Logger.java:2277)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.jboss.logging.Logger.getMessageLogger(Logger.java:2241)
> at org.jboss.logging.Logger.getMessageLogger(Logger.java:2228)
> at org.hibernate.cfg.Configuration.<clinit>(Configuration.java:176)
> ...
> {code}
> This is caused by the fact that all JBoss providers are not public classes and are instead package classes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFCORE-4153) Capability 'org.wildfly.nosql.mongo.driver-service' is unknown error thrown on WildFly 14 + current master branch
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFCORE-4153?page=com.atlassian.jira.plugi... ]
Brian Stansberry edited comment on WFCORE-4153 at 10/5/18 9:51 PM:
-------------------------------------------------------------------
OK, I see the problem.
WFCORE-3751 broke this by discarding the information from the dependent capability passed to the attribute definition builder as to whether it is a dynamic capability and having DefaultCapabilityReferenceRecorder instead figure that out from re-looking up the cap from the MRR. But that lookup will only work if the MRR for the AD is the same as the one that registers the capability. That's not the case in the mongodb subsystem, where it's the subsystem root the registers the dependent cap, and the HostDefinition child that registers the AD.
A possible simple thing to improve this is to not discard the fact that a dependent is NOT dynamic. AIUI the problem WFCORE-3751 was fixing was with how dynamic dependents were handled.
was (Author: brian.stansberry):
OK, I see the problem.
> Capability 'org.wildfly.nosql.mongo.driver-service' is unknown error thrown on WildFly 14 + current master branch
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4153
> URL: https://issues.jboss.org/browse/WFCORE-4153
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 6.0.1.Final
> Reporter: Scott Marlow
> Assignee: Jeff Mesnil
> Priority: Major
>
> As reported on [https://issues.jboss.org/browse/WFNOSQL-28], the wildfly-nosql subsystems are failing on WF14. I will try to work around the failure, following Brian's advice but would still like to see this resolved for other (externally created) subsystems that might hit it.
> Example of failure:
> {quote}
> 2018-10-04 11:09:17,904 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool – 10) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "mongodb"),("mongo" => "default"),("host" => "default")
> ]): java.lang.IllegalStateException: WFLYCTL0364: Capability 'org.wildfly.nosql.mongo.driver-service' is unknown.
> at org.jboss.as.controller.CapabilityReferenceRecorder$DefaultCapabilityReferenceRecorder.getDependentName(CapabilityReferenceRecorder.java:139)
> at org.jboss.as.controller.CapabilityReferenceRecorder$ContextDependencyRecorder.processCapabilityRequirement(CapabilityReferenceRecorder.java:196)
> at org.jboss.as.controller.CapabilityReferenceRecorder$ContextDependencyRecorder.addCapabilityRequirements(CapabilityReferenceRecorder.java:182)
> at org.jboss.as.controller.AttributeDefinition.addCapabilityRequirements(AttributeDefinition.java:1066)
> at org.jboss.as.controller.AbstractAddStepHandler.recordCapabilitiesAndRequirements(AbstractAddStepHandler.java:291)
> at org.jboss.as.controller.AbstractAddStepHandler.execute(AbstractAddStepHandler.java:154)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFCORE-4153) Capability 'org.wildfly.nosql.mongo.driver-service' is unknown error thrown on WildFly 14 + current master branch
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFCORE-4153?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-4153:
------------------------------------------
OK, I see the problem.
> Capability 'org.wildfly.nosql.mongo.driver-service' is unknown error thrown on WildFly 14 + current master branch
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4153
> URL: https://issues.jboss.org/browse/WFCORE-4153
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 6.0.1.Final
> Reporter: Scott Marlow
> Assignee: Jeff Mesnil
> Priority: Major
>
> As reported on [https://issues.jboss.org/browse/WFNOSQL-28], the wildfly-nosql subsystems are failing on WF14. I will try to work around the failure, following Brian's advice but would still like to see this resolved for other (externally created) subsystems that might hit it.
> Example of failure:
> {quote}
> 2018-10-04 11:09:17,904 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool – 10) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "mongodb"),("mongo" => "default"),("host" => "default")
> ]): java.lang.IllegalStateException: WFLYCTL0364: Capability 'org.wildfly.nosql.mongo.driver-service' is unknown.
> at org.jboss.as.controller.CapabilityReferenceRecorder$DefaultCapabilityReferenceRecorder.getDependentName(CapabilityReferenceRecorder.java:139)
> at org.jboss.as.controller.CapabilityReferenceRecorder$ContextDependencyRecorder.processCapabilityRequirement(CapabilityReferenceRecorder.java:196)
> at org.jboss.as.controller.CapabilityReferenceRecorder$ContextDependencyRecorder.addCapabilityRequirements(CapabilityReferenceRecorder.java:182)
> at org.jboss.as.controller.AttributeDefinition.addCapabilityRequirements(AttributeDefinition.java:1066)
> at org.jboss.as.controller.AbstractAddStepHandler.recordCapabilitiesAndRequirements(AbstractAddStepHandler.java:291)
> at org.jboss.as.controller.AbstractAddStepHandler.execute(AbstractAddStepHandler.java:154)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
