[JBoss JIRA] (DROOLS-3085) Fix Scenario.getDescription() access
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-3085:
----------------------------------------
Summary: Fix Scenario.getDescription() access
Key: DROOLS-3085
URL: https://issues.jboss.org/browse/DROOLS-3085
Project: Drools
Issue Type: Bug
Components: Scenario Simulation and Testing
Reporter: Gabriele Cardosi
Assignee: Daniele Zonca
accessing Scenario.getDescription() throws exception. Refactor to avoid that *or* catch all throwned exceptions.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (JGRP-2299) LockService does not work correctly if unlock/lock is called in immediate succession
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2299?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2299:
---------------------------
Fix Version/s: 4.0.16
> LockService does not work correctly if unlock/lock is called in immediate succession
> ------------------------------------------------------------------------------------
>
> Key: JGRP-2299
> URL: https://issues.jboss.org/browse/JGRP-2299
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.15
> Environment: Windows 10 Oracle JDK 1.8 131
> AIX IBM Java 8
> Reporter: Mirko Streckenbach
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.0.16
>
> Attachments: JGroupsExample.java, udp+lock.xml
>
>
> In our application we have encountered occasional cases of LockService allowing 2 processes to hold the same lock at the same time. I could reproduce this with a simple program (see atttachment) and it happens if for a lock "unlock" is called and immediately afterwards "lock". If there is a small delay (e.g. 1 second) between the two operations everything works as expected.
> This can be produced with the attached program. The program does lock/unlock/lock on a lock and then tries to lock the same lock from a different JChannel and is awarded the lock. If you place a small sleep() after the unlock, everything works as expected and the parallel lock is not awarded.
> If you turn on debugging you'll see no output between unlock and lock, so it looks to me like the lock is awarded without passing GRANT_LOCK messages to the stack. Using a conditional break point you can see that ClientLock.acquired is still true even after the unlock().
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11131) @LoginToContinue.errorPage doesn't work for pages in WEB-INF (New Java EE 8 Security)
by Instantiation Exception (Jira)
[ https://issues.jboss.org/browse/WFLY-11131?page=com.atlassian.jira.plugin... ]
Instantiation Exception commented on WFLY-11131:
------------------------------------------------
It is possible that this is correct behavior. Spec says (https://javaee.github.io/security-spec/spec/jsr375-spec.html#_logintocont...)
{quote}
(...)
Redirect or forward to LoginToContinue.loginPage(), depending on the value of the useForwardToLogin() attribute.
(...)
If LoginToContinue.errorPage() is non-null and non-empty, redirect to LoginToContinue.errorPage().
(...)
{quote}
> @LoginToContinue.errorPage doesn't work for pages in WEB-INF (New Java EE 8 Security)
> -------------------------------------------------------------------------------------
>
> Key: WFLY-11131
> URL: https://issues.jboss.org/browse/WFLY-11131
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 14.0.1.Final
> Reporter: Instantiation Exception
> Assignee: Darran Lofthouse
> Priority: Major
>
> I have this configuration:
> {code:java}
> @FormAuthenticationMechanismDefinition(
> loginToContinue = @LoginToContinue(
> loginPage = "/WEB-INF/account/login.xhtml",
> errorPage = "/WEB-INF/account/login.xhtml?error=true"))
> @ApplicationScoped
> public class SecurityConfiguration {}
> {code}
> When I open browser and go to restricted page, I am forwarded to login page. Then I input invalid username and password and submit form (action="j_security_check"). My browser sends me redirect to http://localhost:8080/WEB-INF/account/login.xhtml?error=true. I believe it should forward request to /WEB-INF/account/login.xhtml?error=true because standard FORM login-config in web.xml worked this way.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11131) @LoginToContinue.errorPage doesn't work for pages in WEB-INF (New Java EE 8 Security)
by Instantiation Exception (Jira)
Instantiation Exception created WFLY-11131:
----------------------------------------------
Summary: @LoginToContinue.errorPage doesn't work for pages in WEB-INF (New Java EE 8 Security)
Key: WFLY-11131
URL: https://issues.jboss.org/browse/WFLY-11131
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 14.0.1.Final
Reporter: Instantiation Exception
Assignee: Darran Lofthouse
I have this configuration:
{code:java}
@FormAuthenticationMechanismDefinition(
loginToContinue = @LoginToContinue(
loginPage = "/WEB-INF/account/login.xhtml",
errorPage = "/WEB-INF/account/login.xhtml?error=true"))
@ApplicationScoped
public class SecurityConfiguration {}
{code}
When I open browser and go to restricted page, I am forwarded to login page. Then I input invalid username and password and submit form (action="j_security_check"). My browser sends me redirect to http://localhost:8080/WEB-INF/account/login.xhtml?error=true. I believe it should forward request to /WEB-INF/account/login.xhtml?error=true because standard FORM login-config in web.xml worked this way.
--
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 David Lloyd (Jira)
[ https://issues.jboss.org/browse/JBLOGGING-111?page=com.atlassian.jira.plu... ]
David Lloyd commented on JBLOGGING-111:
---------------------------------------
It sounds more like what you want is a way to use some configuration other than a system property in order to choose one of the preexisting providers. You are trying to use service loader as this configuration mechanism, though that's not really an appropriate solution for choosing a provider because it's meant for _providing_ a provider.
I think it's reasonable to open a new JIRA which is a feature request to support the specification of a preexisting provider on a class loader (aka per-application) basis. I don't think it's a good idea to make implementation classes public in order to facilitate that feature. But that discussion can be had in the new JIRA.
> 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] (WFLY-11129) Temporary files not cleaned up after build
by Frank Langelage (Jira)
Frank Langelage created WFLY-11129:
--------------------------------------
Summary: Temporary files not cleaned up after build
Key: WFLY-11129
URL: https://issues.jboss.org/browse/WFLY-11129
Project: WildFly
Issue Type: Bug
Affects Versions: 14.0.1.Final
Environment: Solaris SPARC 10, Oracle JDK 1.80,0_181
Reporter: Frank Langelage
Assignee: Jason Greene
After building WildFly 14 from sources I have a lot of files in /var/tmp folder under a unique folder.
{{sb2000.[neu2l]/mbi/mbi2e_all. ls -l /var/tmp
total 5356
drwxr-xr-x 3 jboss informix 512 Oct 6 14:47 1397ea75-a91c-490a-9860-0041c101ef3a
drwxr-xr-x 3 jboss informix 512 Oct 6 13:47 23d28bb9-0bdd-4991-aa9b-8805d613e720
drwxr-xr-x 3 jboss informix 512 Oct 5 23:34 2c3bd18e-8b83-46d3-b06f-18378e1cb12d
drwxr-xr-x 3 jboss informix 512 Oct 6 14:56 396f75f7-45b0-4b50-9607-9060cabf018b
drwxr-xr-x 3 jboss informix 512 Oct 6 13:48 521e2a76-764c-4f5a-8a6e-282dd5978991
drwxr-xr-x 3 jboss informix 512 Oct 5 23:35 5430e295-1afa-4257-a2e0-e08b980b7e35
drwxr-xr-x 3 jboss informix 512 Oct 6 14:53 5a265551-8f04-48c9-8945-abf830e54852
drwxr-xr-x 3 jboss informix 512 Oct 6 13:46 70a1f863-7e84-40df-9206-23690bcf3ef6
drwxr-xr-x 3 jboss informix 512 Oct 5 22:02 7186627a-5a89-4334-bdc2-8bfb944e3841
drwxr-xr-x 3 jboss informix 512 Oct 6 14:52 85663b19-7e4e-48e9-8988-bd24c11fe4d4
drwxr-xr-x 3 jboss informix 512 Oct 5 23:39 8842f374-85b7-4018-a1fc-6274cb704785
drwxr-xr-x 3 jboss informix 512 Oct 5 22:05 973d7e32-efe5-4ffa-8f02-079cb7f29e71
drwxr-x--- 3 oracle dba 2560 Aug 30 00:00 CVU_18.0.0.0.0_oracle
drwxr-xr-x 3 jboss informix 512 Oct 5 22:06 b8975817-9381-41a3-a512-e8fc6596fa7a
drwxr-xr-x 3 jboss informix 512 Oct 6 13:40 bd0c1dd7-e8c6-413d-b658-f3c5236bba34
drwxr-xr-x 3 jboss informix 512 Oct 6 14:54 c3aa3f01-66df-4066-bb35-fed4bd0ad559
drwxr-xr-x 3 jboss informix 512 Oct 5 23:32 c66c2972-ad28-49e9-a7ff-a7ceed5b7ea3
drwxr-xr-x 3 jboss informix 512 Oct 5 23:24 ca8816d8-ad10-4860-a18b-0c09b37ed88b
drwxr-xr-x 3 jboss informix 512 Oct 6 13:50 cc799f82-ed02-4dc4-b56e-ffe0d8eeab75
drwx------ 2 langfr staff 512 Nov 15 2006 orbit-lafr
-rw-rw-rw- 1 langfr staff 2383862 Oct 5 03:17 patchdiag.xref
-rw------- 1 root root 314461 Oct 6 15:32 wscon-:0-5saqic}}
{{sb2000.[neu2l]/var/tmp. ls -l 396f75f7-45b0-4b50-9607-9060cabf018b/maven/org.jboss.universe_community-universe/*/current
396f75f7-45b0-4b50-9607-9060cabf018b/maven/org.jboss.universe_community-universe/wildfly-core/current:
total 2
drwxr-xr-x 7 jboss informix 512 Oct 6 14:55 6.0.2.Final
396f75f7-45b0-4b50-9607-9060cabf018b/maven/org.jboss.universe_community-universe/wildfly-servlet/current:
total 2
drwxr-xr-x 6 jboss informix 512 Oct 6 14:55 14.0.1.Final
396f75f7-45b0-4b50-9607-9060cabf018b/maven/org.jboss.universe_community-universe/wildfly/current:
total 2
drwxr-xr-x 6 jboss informix 512 Oct 6 14:55 14.0.1.Final}}
Created by galleon feature pack build (galleon-pack/wildfly-feature-pack-build.xml).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11128) wsconsume failure on wildfly14 + JDK 11
by mazen mahmoud (Jira)
mazen mahmoud created WFLY-11128:
------------------------------------
Summary: wsconsume failure on wildfly14 + JDK 11
Key: WFLY-11128
URL: https://issues.jboss.org/browse/WFLY-11128
Project: WildFly
Issue Type: Bug
Components: CLI
Affects Versions: 14.0.0.Final
Environment: Windows 7 64bits
JDK 11
Wildfly 14
Reporter: mazen mahmoud
Assignee: Jean-Francois Denise
Attachments: log.txt
running wsconsume on a single jax-ws service with JDK 11 failes. (see attached log.txt file)
the service is very simple.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11121) CI - Master linux JDK 11 job - compilation fails - forked embedded process has failed
by Alexey Loubyansky (Jira)
[ https://issues.jboss.org/browse/WFLY-11121?page=com.atlassian.jira.plugin... ]
Alexey Loubyansky commented on WFLY-11121:
------------------------------------------
I've released Galleon and WFGP 2.0.1.Final that fixes this. The PRs integrating them for Core and WF are
WFCORE-4155 https://github.com/wildfly/wildfly-core/pull/3545
WFLY-11126 https://github.com/wildfly/wildfly/pull/11719
The integration tests in Core CI fail due to the Galleon and WFGP version conflict between WildFly Core and WildFly Full. There are two ways to proceed:
1) merge the corresponding PR for WildFly wildfly/wildfly#11719;
2) include WildFly provisioning plugin into Servlet feature-pack and not inherit it from Core.
Either way it requires a change in WildFly Full build though.
> CI - Master linux JDK 11 job - compilation fails - forked embedded process has failed
> --------------------------------------------------------------------------------------
>
> Key: WFLY-11121
> URL: https://issues.jboss.org/browse/WFLY-11121
> Project: WildFly
> Issue Type: Bug
> Reporter: Rostislav Svoboda
> Assignee: Alexey Loubyansky
> Priority: Blocker
> Labels: Java11
>
> Compilation of Master linux JDK 11 job fails - forked embedded process has failed.
> https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxJdk11
> {code}
> [Step 2/3] [ERROR] Failed to execute goal org.wildfly.galleon-plugins:wildfly-galleon-maven-plugin:
> 2.0.0.Final:generate-feature-specs (feature-spec-build) on project wildfly-servlet-galleon-pack:
> Feature spec generator failed: Forked embedded process has failed -> [Help 1]
> {code}
> My local machine runs are passing for me, using {{java version "11" 2018-09-25 (build 11+28)}}
> This fail can be related to VMs setup on TeamCity, another option can be galleon related issue.
> CCing also [~aloubyansky]
> We need to have valid Java 11 runs on upstream to guard proper functionality of WildFly.
--
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)
[ 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
---------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...]
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
[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...]
> 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
> ---------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, 7 months
