[JBoss JIRA] (WFLY-11432) EAR (WAR + EJB JAR) fails to be deployed with CNFE from open tracing
by Matej Novotny (Jira)
[ https://issues.jboss.org/browse/WFLY-11432?page=com.atlassian.jira.plugin... ]
Matej Novotny updated WFLY-11432:
---------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/11902
> EAR (WAR + EJB JAR) fails to be deployed with CNFE from open tracing
> --------------------------------------------------------------------
>
> Key: WFLY-11432
> URL: https://issues.jboss.org/browse/WFLY-11432
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing
> Affects Versions: 14.0.0.Final, 15.0.0.Beta1
> Reporter: Jan Stourac
> Assignee: Matej Novotny
> Priority: Critical
>
> Upon deployment of an example app from weld examples, there is CNFE from open tracing during the deployment of an EAR (WAR + EJB JAR) artifact. [~manovotn] has already done some investigation and sent his findings to [wildfly-dev mailing list|http://lists.jboss.org/pipermail/wildfly-dev/2018-November/006716.html].
> Problematic Weld example test is [this one|https://github.com/weld/core/blob/master/examples/jsf/translator/ftes...].
> {code}
> 2018-11-28 14:35:36,063 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."weld-translator.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."weld-translator.ear".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> 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)
> Caused by: org.jboss.weld.resources.spi.ResourceLoadingException: Error while loading class org.wildfly.microprofile.opentracing.smallrye.TracerProducer$Proxy$_$$_WeldSubclass
> at org.jboss.weld.resources.ClassTransformer.getBackedAnnotatedType(ClassTransformer.java:186)
> at org.jboss.weld.resources.ClassTransformer.getBackedAnnotatedType(ClassTransformer.java:194)
> at org.jboss.weld.resources.ClassTransformer.getEnhancedAnnotatedType(ClassTransformer.java:232)
> at org.jboss.weld.injection.producer.SubclassedComponentInstantiator.initEnhancedSubclass(SubclassedComponentInstantiator.java:86)
> at org.jboss.weld.injection.producer.SubclassedComponentInstantiator.<init>(SubclassedComponentInstantiator.java:79)
> at org.jboss.weld.injection.producer.SubclassedComponentInstantiator.forInterceptedDecoratedBean(SubclassedComponentInstantiator.java:63)
> at org.jboss.weld.injection.producer.BeanInjectionTarget.initializeAfterBeanDiscovery(BeanInjectionTarget.java:121)
> at org.jboss.weld.injection.producer.InjectionTargetInitializationContext.initialize(InjectionTargetInitializationContext.java:42)
> at org.jboss.weld.injection.producer.InjectionTargetService.initialize(InjectionTargetService.java:63)
> at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:475)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:86)
> at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:97)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> ... 6 more
> Caused by: java.lang.NoClassDefFoundError: io/opentracing/Tracer
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
> at java.lang.Class.getDeclaredMethods(Class.java:1975)
> at org.jboss.weld.annotated.slim.backed.SecurityActions.getDeclaredMethods(SecurityActions.java:41)
> at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$BackedAnnotatedMethods.computeValue(BackedAnnotatedType.java:197)
> at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$BackedAnnotatedMethods.computeValue(BackedAnnotatedType.java:191)
> at org.jboss.weld.util.LazyValueHolder.get(LazyValueHolder.java:46)
> at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$EagerlyInitializedLazyValueHolder.<init>(BackedAnnotatedType.java:159)
> at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$BackedAnnotatedMethods.<init>(BackedAnnotatedType.java:191)
> at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType$BackedAnnotatedMethods.<init>(BackedAnnotatedType.java:191)
> at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType.<init>(BackedAnnotatedType.java:66)
> at org.jboss.weld.annotated.slim.backed.BackedAnnotatedType.of(BackedAnnotatedType.java:47)
> at org.jboss.weld.resources.ClassTransformer$TransformClassToBackedAnnotatedType.apply(ClassTransformer.java:84)
> at org.jboss.weld.resources.ClassTransformer$TransformClassToBackedAnnotatedType.apply(ClassTransformer.java:79)
> at org.jboss.weld.util.cache.ReentrantMapBackedComputingCache.lambda$null$0(ReentrantMapBackedComputingCache.java:55)
> at org.jboss.weld.util.WeakLazyValueHolder$1.computeValue(WeakLazyValueHolder.java:35)
> at org.jboss.weld.util.WeakLazyValueHolder.get(WeakLazyValueHolder.java:53)
> at org.jboss.weld.util.cache.ReentrantMapBackedComputingCache.getValue(ReentrantMapBackedComputingCache.java:72)
> at org.jboss.weld.util.cache.ReentrantMapBackedComputingCache.getCastValue(ReentrantMapBackedComputingCache.java:78)
> at org.jboss.weld.resources.ClassTransformer.getBackedAnnotatedType(ClassTransformer.java:177)
> ... 19 more
> Caused by: java.lang.ClassNotFoundException: io.opentracing.Tracer from [Module "deployment.weld-translator.ear" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> ... 39 more
> 2018-11-28 14:35:36,073 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "weld-translator.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"weld-translator.ear\".WeldStartService" => "Failed to start service
> Caused by: org.jboss.weld.resources.spi.ResourceLoadingException: Error while loading class org.wildfly.microprofile.opentracing.smallrye.TracerProducer$Proxy$_$$_WeldSubclass
> Caused by: java.lang.NoClassDefFoundError: io/opentracing/Tracer
> Caused by: java.lang.ClassNotFoundException: io.opentracing.Tracer from [Module \"deployment.weld-translator.ear\" from Service Module Loader]"}}
> 2018-11-28 14:35:36,076 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "weld-translator.ear" was rolled back with the following failure message:
> {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"weld-translator.ear\".WeldStartService" => "Failed to start service
> Caused by: org.jboss.weld.resources.spi.ResourceLoadingException: Error while loading class org.wildfly.microprofile.opentracing.smallrye.TracerProducer$Proxy$_$$_WeldSubclass
> Caused by: java.lang.NoClassDefFoundError: io/opentracing/Tracer
> Caused by: java.lang.ClassNotFoundException: io.opentracing.Tracer from [Module \"deployment.weld-translator.ear\" from Service Module Loader]"}}
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (DROOLS-3387) Update interaction behavior to align with DMN/Stunner.
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3387?page=com.atlassian.jira.plugi... ]
Klara Kufova commented on DROOLS-3387:
--------------------------------------
[~uxdlc], looks good to me. If the single click to select a cell will be different from the single click to launch a pop-over (one will be a right click and the other a left click), I think it is sufficient.
> Update interaction behavior to align with DMN/Stunner.
> -------------------------------------------------------
>
> Key: DROOLS-3387
> URL: https://issues.jboss.org/browse/DROOLS-3387
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Daniele Zonca
> Priority: Major
> Labels: UX, UXTeam
>
> Align grid interactions to be consistent with DMN updates:
> - Single-click to select a cell
> - double-click to edit a cell inline.
> - single click to launch a pop-over menu.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (WFLY-10929) Unescaped characters in URL from client does not work correctly when allowed for HTTP and HTTPS listeners
by Bartosz Baranowski (Jira)
[ https://issues.jboss.org/browse/WFLY-10929?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski updated WFLY-10929:
--------------------------------------
Steps to Reproduce:
# unzip WildFly and start via ./bin/standalone.sh
# in CLI perform following operations:
{code}
/subsystem=undertow/server=default-server/host=default-host/setting=access-log:add()
/subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=allow-unescaped-characters-in-url,value=true)
/subsystem=undertow/server=default-server/https-listener=https:write-attribute(name=allow-unescaped-characters-in-url,value=true)
/subsystem=undertow/server=default-server/host=default-host/setting=access-log:write-attribute(name=use-server-log, value=true)
deploy helloworld.war
reload
{code}
# Now try to access WildFly server:
{code}
# First against HTTP listener:
curl "http://localhost:8080/helloworld/한글이름_test.html?param=한글이름_ahoy" -v >/dev/null
# Check result in access log
# Now try against HTTPS listener:
curl "https://localhost:8443/helloworld/한글이름_test.html?param=한글이름_ahoy" -v >/dev/null --insecure
# Check result in access log
{code}
was:
# unzip WildFly and start via ./bin/standalone.sh
# in CLI perform following operations:
{code}
/subsystem=undertow/server=default-server/host=default-host/setting=access-log:add()
/subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=allow-unescaped-characters-in-url,value=true)
/subsystem=undertow/server=default-server/https-listener=https:write-attribute(name=allow-unescaped-characters-in-url,value=true)
/subsystem=undertow/server=default-server/host=default-host/setting=access-log:add(use-server-log=true)
deploy helloworld.war
reload
{code}
# Now try to access WildFly server:
{code}
# First against HTTP listener:
curl "http://localhost:8080/helloworld/한글이름_test.html?param=한글이름_ahoy" -v >/dev/null
# Check result in access log
# Now try against HTTPS listener:
curl "https://localhost:8443/helloworld/한글이름_test.html?param=한글이름_ahoy" -v >/dev/null --insecure
# Check result in access log
{code}
> Unescaped characters in URL from client does not work correctly when allowed for HTTP and HTTPS listeners
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10929
> URL: https://issues.jboss.org/browse/WFLY-10929
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 14.0.0.Beta2
> Reporter: Jan Stourac
> Assignee: Bartosz Baranowski
> Priority: Major
> Attachments: helloworld.war
>
>
> Since the time of {{EAP7.1.1.CP}} there is a possibility to allow unescaped characters in URL requests from clients to server. This was allowed first by setting {{org.wildfly.undertow.ALLOW_UNESCAPED_CHARACTERS_IN_URL=true}} system property introduced by UNDERTOW-1185. Now we have a new attribute for this in Wildfly in AJP, HTTP and HTTPS listeners {{allow-unescaped-characters-in-url}}.
> However this does not seem to work correctly. There have been some fixes for AJP listener already UNDERTOW-1386, UNDERTOW-1386 and UNDERTOW-1399 (the last one not included in WildFly {{14.0.0.Beta2}} yet). However HTTP/HTTPS listener seems to be broken too.
> When HTTP request with unescaped characters is performed against server:
> {code}
> curl "http://localhost:8080/helloworld/한글이름_test.html?param=한글이름_ahoy" -v >/dev/null
> {code}
> we get 200 OK HTTP response, although the result in access log looks like:
> {code:title=HTTP actual result}
> 127.0.0.1 - - [27/Aug/2018:09:17:39 +0200] "GET /helloworld/íê¸ì´ë¦
> _test.html?param=íê¸ì´ë¦
> _ahoy HTTP/1.1" 200 950
> {code}
> but we expect following:
> {code:title=HTTP expected result}
> 127.0.0.1 - - [27/Aug/2018:08:40:47 +0200] "GET /helloworld/한글이름_test.html?param=한글이름_ahoy HTTP/1.1" 200 950
> {code}
> Slightly different problem seems to be also for HTTPS listener. When we perform HTTPS request against WildFly:
> {code}
> curl "https://localhost:8443/helloworld/한글이름_test.html?param=한글이름_ahoy" -v >/dev/null --insecure
> {code}
> we receive 404 Not Found HTTP response and following record in access.log:
> {code:HTTPS actual result}
> 127.0.0.1 - - [27/Aug/2018:09:18:37 +0200] "GET /helloworld/￭ﾕﾜ￪ﾸﾀ￬ﾝﾴ￫ﾦﾄ_test.html?param=￭ﾕﾜ￪ﾸﾀ￬ﾝﾴ￫ﾦﾄ_ahoy HTTP/2.0" 404 68
> {code}
> however expected result should be similar to what we expect for HTTP, I guess.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (DROOLS-3385) Stateful session is not thread safe for update operation on JDK11
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-3385?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-3385:
--------------------------------
Sprint: 2018 Week 48-50
> Stateful session is not thread safe for update operation on JDK11
> -----------------------------------------------------------------
>
> Key: DROOLS-3385
> URL: https://issues.jboss.org/browse/DROOLS-3385
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.16.0.Final
> Reporter: Radovan Synek
> Assignee: Mario Fusco
> Priority: Critical
>
> We have a test failure in multithreaded solving in OptaPlanner (please see the linked issue for details). Interestingly, it happens only with JDK11.
> java.util.ConcurrentModificationException: null
> at java.base/java.util.HashMap.computeIfAbsent(HashMap.java:1134)
> at org.drools.core.impl.KnowledgeBaseImpl.getOrCreateExactTypeDeclaration(KnowledgeBaseImpl.java:1458)
> at org.drools.core.common.NamedEntryPoint.update(NamedEntryPoint.java:324)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.update(StatefulKnowledgeSessionImpl.java:1570)
> at org.optaplanner.core.impl.score.director.drools.DroolsScoreDirector.update(DroolsScoreDirector.java:254)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (WFLY-11340) Tests in org.jboss.as.test.integration.microprofile.opentracing failing with security manager
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFLY-11340?page=com.atlassian.jira.plugin... ]
Marek Kopecký commented on WFLY-11340:
--------------------------------------
[~jamezp] (cc [~asoldano], [~rsearls], [~jbliznak]):
{quote}an issue for JAX-RS{quote}
WF uses jboss jaxrs implementation: https://github.com/jboss/jboss-jaxrs-api_spec/blob/master/src/main/java/j...
{noformat}
[mkopecky@dhcp-10-40-5-71 wfly]$ find | grep jaxrs | grep jar$ | grep spec
./modules/system/layers/base/javax/ws/rs/api/main/jboss-jaxrs-api_2.1_spec-1.0.2.Final.jar
[mkopecky@dhcp-10-40-5-71 wfly]$
{noformat}
Wouldn't be better to fill the issue to https://github.com/jboss/jboss-jaxrs-api_spec/issues or to [JBEE jira project|https://issues.jboss.org/projects/JBEE]?
{quote} PR with FasterXML.{quote}
FasterXML (Jackson2) is old (not ee8 compliant) json provider in resteasy. Wouldn't be better to use JSON-B (yasson, ee8 compliant) here?
> Tests in org.jboss.as.test.integration.microprofile.opentracing failing with security manager
> ---------------------------------------------------------------------------------------------
>
> Key: WFLY-11340
> URL: https://issues.jboss.org/browse/WFLY-11340
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing, Test Suite
> Affects Versions: 14.0.0.Final
> Reporter: Martin Choma
> Assignee: Jan Stourac
> Priority: Major
> Labels: security-manager
>
> These tests fail with security manager from package org.jboss.as.test.integration.microprofile.opentracing
> * ResourceNotTracedTestCase.notTracedEndpointYieldsNoSpans
> * ResourceTracedTestCase.tracedEndpointYieldsSpan
> * ResourceWithCDITestCase.tracedEndpointYieldsSpan
> * ResourceWithCustomOperationNameBeanTestCase.customOperationName
> * SimpleRestClientTestCase.clientRequestSpanJoinsServer
> {noformat}
> java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "modifyThread")" in code source "(vfs:/content/3f3aff01-8e62-42e9-81c0-022f693ec7e0.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.3f3aff01-8e62-42e9-81c0-022f693ec7e0.war" from Service Module Loader")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:294)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:191)
> at java.util.concurrent.ThreadPoolExecutor.checkShutdownAccess(ThreadPoolExecutor.java:742)
> at java.util.concurrent.ThreadPoolExecutor.shutdownNow(ThreadPoolExecutor.java:1429)
> at java.util.concurrent.Executors$DelegatedExecutorService.shutdownNow(Executors.java:670)
> at org.jboss.as.test.integration.common.HttpRequest.execute(HttpRequest.java:63)
> at org.jboss.as.test.integration.common.HttpRequest.get(HttpRequest.java:82)
> at org.jboss.as.test.integration.microprofile.opentracing.ResourceNotTracedTestCase.performCall(ResourceNotTracedTestCase.java:63)
> at org.jboss.as.test.integration.microprofile.opentracing.ResourceNotTracedTestCase.notTracedEndpointYieldsNoSpans(ResourceNotTracedTestCase.java:57)
> {noformat}
> As stacktrace is from test side and tests are missing @RunAsClient, I believe tests are running in container. [~juraci.costa] is this really intent tests are missing @RunAsClient annotation?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JGRP-2316) DNS_PING is not using correct ports with SRV based service discovery
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2316?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2316:
--------------------------------
The ports reported by DNS (A or SRV records) are *irrelevant* (in that respect, I think JGRP-2996 is irrelevant, too): the ports are defined in the JGroups config *only*, as Kubernetes/Openshift only knows the IP addresses of the started pods, but not the JGroups ports!
So what DNS_PING does is that it ignores the ports given by DNS, even if they're != 0. Instead, it establishes connections to all IP addresses at range {{[TCP.bind_port .. TCP.bind_port+port_range]}}.
If you don't agree, please show me a concrete example where this algorithm wouldn't work. Meanwhile, I'm taking another look at JGRP-2996.
Cheers,
> DNS_PING is not using correct ports with SRV based service discovery
> --------------------------------------------------------------------
>
> Key: JGRP-2316
> URL: https://issues.jboss.org/browse/JGRP-2316
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.15
> Reporter: dmcnair
> Assignee: Bela Ban
> Priority: Major
>
> This is a follow-up to JGRP-2296 - which changed `DefaultDNSResolver.java` to preserve the port for SRV records. While that change is working as desired, `DNS_PING.java` is not using the port when doing member discovery.
> Here are the log entries using *4.0.15*
> {noformat}
> 2018-11-29 21:37:41,561 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-4,null,null) Entries collected from DNS (in 5 ms): [172.29.11.50:27106, 172.29.11.50:27105]
> 2018-11-29 21:37:41,562 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-4,null,null) 982d38761cba: sending discovery requests to hosts [172.29.11.50:27106, 172.29.11.50:27105] on ports [7600 .. 7600]
> {noformat}
> Since the port was found via the SRV record, it should be used instead of the *transportPort* port.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (WFCORE-4241) remove-identity in filesystem-realm fails when executed before filesystem-realm removal in the same batch
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFCORE-4241?page=com.atlassian.jira.plugi... ]
Chao Wang commented on WFCORE-4241:
-----------------------------------
Cli output error:
{noformat}
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the er
ror):
WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:
Step: step-1
Operation: /subsystem=elytron/filesystem-realm=exampleFsRealm:remove-identity(identity=user)
Failure: WFLYCTL0216: Management resource '[
("subsystem" => "elytron"),
("filesystem-realm" => "exampleFsRealm")
]' not found
{noformat}
Looking at [~jmesnil]'s comment in JBEAP-3187, I think this error happens for the same reason: [RemoveIdentityHandler is a RuntimeOnlyHandler|https://github.com/wildfly/wildfly-core/blob/7.0.0.CR1...], named filesystem-realm model has been removed in 2nd operation Model step before 1st operation Runtime step.
> remove-identity in filesystem-realm fails when executed before filesystem-realm removal in the same batch
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4241
> URL: https://issues.jboss.org/browse/WFCORE-4241
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Diana Vilkolakova
> Priority: Major
> Attachments: add.cli, remove.cli
>
>
> Elytron filesystem-realm has an {{remove-identity}} operation. If executed in the same batch with later removal of said filesystem-realm, the remove-identity operation will fail with error: filesystem-realm not found.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (WFLY-11127) Can not get activemq and undertow subsystem data from HTTP management api
by Lin Gao (Jira)
[ https://issues.jboss.org/browse/WFLY-11127?page=com.atlassian.jira.plugin... ]
Lin Gao resolved WFLY-11127.
----------------------------
Resolution: Rejected
I am rejecting this issue, as change the request format will work.
> 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: Lin Gao
> 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
> ---------8<------------------------------------------8<-----------------------
> 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
> --------->8------------------------------------------>8-----------------------
> And this the query with the GUI client
> [jboss_jms_queue_gui_query|https://user-images.githubusercontent.com/58834...]
> Also with undertow subsystem
> ---------8<------------------------------------------8<-----------------------
> 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
> }
> --------->8------------------------------------------>8-----------------------
> 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
