[JBoss JIRA] (WFLY-11351) Add resource address and attribute name to metric tags
by Jeff Mesnil (Jira)
Jeff Mesnil created WFLY-11351:
----------------------------------
Summary: Add resource address and attribute name to metric tags
Key: WFLY-11351
URL: https://issues.jboss.org/browse/WFLY-11351
Project: WildFly
Issue Type: Enhancement
Components: MP Metrics
Reporter: Jeff Mesnil
Assignee: Jason Greene
Fix For: 15.0.0.CR1
WildFly metrics are exposed as Microprofile Metrics with unique names composed of the resource address and the attribute name.
This can lead to very long unhelpful names. For example, the request-count metric on the /deployment=example.war/subsystem=undertow/servlet=org.example.MyServlet resource is named is registered as `deployment/example.war/subsystem/undertow/servlet/org.example.MyServlet/request-count`.
When the metric is exported to Prometheus format, it becomes `deployment_example_war_subsystem_undertow_servlet_org_example_my_servlet_request_count` which is a mouthful.
In order to simply query and aggregation of metrics, the resource address and the attribute name will be stored in the metric tags.
E.g. for the metric above, its tags will be:
* subsystem="undertow"
* deployment="example.war"
* servlet="org.example.MyServlet"
* attribute="request-count"
This makes it much simple for example to aggregate all metrics from a given deployment by looking at metrics with the tag deployment="example.war".
Note hower that the tags does not preserve the order of the resource address' elements.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11288) Missing proton SaslListener
by ehsavoie Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFLY-11288?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet resolved WFLY-11288.
--------------------------------------
Resolution: Duplicate Issue
> Missing proton SaslListener
> ---------------------------
>
> Key: WFLY-11288
> URL: https://issues.jboss.org/browse/WFLY-11288
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Reporter: Karl Sorensen
> Assignee: ehsavoie Hugonnet
> Priority: Major
>
> When trying to use an external client to connect to ActiveMQ/Artemis instance using the AMQP protocol an SASL exception is thrown.
> 2018-11-05 12:08:01,636 TRACE [org.jboss.modules] (Thread-1 (activemq-netty-threads)) Class org.apache.qpid.proton.engine.SaslListener not found from Module "org.apache.activemq.artemis.protocol.amqp" from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /apps/wildfly14.0/modules,/apps/wildfly14.0/modules/system/layers/base))
> Issue can be resolved by manually including proton-j-0.27.3.jar into the org.apache.activemq.artemis.protocol.amqp module as discussed in the attached forum post.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11288) Missing proton SaslListener
by ehsavoie Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFLY-11288?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet reassigned WFLY-11288:
----------------------------------------
Assignee: ehsavoie Hugonnet (was: Jeff Mesnil)
> Missing proton SaslListener
> ---------------------------
>
> Key: WFLY-11288
> URL: https://issues.jboss.org/browse/WFLY-11288
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Reporter: Karl Sorensen
> Assignee: ehsavoie Hugonnet
> Priority: Major
>
> When trying to use an external client to connect to ActiveMQ/Artemis instance using the AMQP protocol an SASL exception is thrown.
> 2018-11-05 12:08:01,636 TRACE [org.jboss.modules] (Thread-1 (activemq-netty-threads)) Class org.apache.qpid.proton.engine.SaslListener not found from Module "org.apache.activemq.artemis.protocol.amqp" from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /apps/wildfly14.0/modules,/apps/wildfly14.0/modules/system/layers/base))
> Issue can be resolved by manually including proton-j-0.27.3.jar into the org.apache.activemq.artemis.protocol.amqp module as discussed in the attached forum post.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11340) Tests in org.jboss.as.test.integration.microprofile.opentracing failing with security manager
by Juraci Paixão Kröhling (Jira)
[ https://issues.jboss.org/browse/WFLY-11340?page=com.atlassian.jira.plugin... ]
Juraci Paixão Kröhling commented on WFLY-11340:
-----------------------------------------------
At this point, I think [~jstourac] knows more about the tests than I do :-)
> 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: Test Suite
> Affects Versions: 14.0.0.Final
> Reporter: Martin Choma
> Priority: Major
>
> 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, 8 months
[JBoss JIRA] (SWSQE-500) Kiali-UI PRT Run UI Tests
by Hayk Hovsepyan (Jira)
Hayk Hovsepyan created SWSQE-500:
------------------------------------
Summary: Kiali-UI PRT Run UI Tests
Key: SWSQE-500
URL: https://issues.jboss.org/browse/SWSQE-500
Project: Kiali QE
Issue Type: QE Task
Reporter: Hayk Hovsepyan
Assignee: Hayk Hovsepyan
As Kiali-UI repo PRT does not require e2e tests to be run, the job could me modified to run PRT of Python-UI tests and run then on request, typing 'kialiqeci' in PR comment.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11350) Test DefaultElytronEjbSecurityDomainTestCase fails with security manager
by Martin Choma (Jira)
Martin Choma created WFLY-11350:
-----------------------------------
Summary: Test DefaultElytronEjbSecurityDomainTestCase fails with security manager
Key: WFLY-11350
URL: https://issues.jboss.org/browse/WFLY-11350
Project: WildFly
Issue Type: Bug
Components: Test Suite
Affects Versions: 14.0.0.Final
Reporter: Martin Choma
{noformat}
org.wildfly.test.integration.elytron.ejb (1)
DefaultElytronEjbSecurityDomainTestCase.testSecurityOnTwoBeansInAbsenceOfExplicitSecurityDomain
{noformat}
{noformat}
java.security.AccessControlException: WFSM000001: Permission check failed (permission "("org.wildfly.security.permission.ElytronPermission" "authenticate")" in code source "(vfs:/content/ejb-security-domain-test.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.ejb-security-domain-test.jar" 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 org.wildfly.security.auth.server.SecurityDomain.authenticate(SecurityDomain.java:304)
at org.wildfly.security.auth.server.SecurityDomain.authenticate(SecurityDomain.java:285)
at org.jboss.as.test.shared.integration.ejb.security.Util.switchIdentity(Util.java:242)
at org.jboss.as.test.shared.integration.ejb.security.Util.switchIdentity(Util.java:206)
at org.jboss.as.test.shared.integration.ejb.security.Util.switchIdentitySCF(Util.java:302)
at org.wildfly.test.integration.elytron.ejb.DefaultElytronEjbSecurityDomainTestCase.testSecurityOnTwoBeansInAbsenceOfExplicitSecurityDomain(DefaultElytronEjbSecurityDomainTestCase.java:104)
{noformat}
That helps
{noformat}
diff --git a/testsuite/integration/elytron/src/test/java/org/wildfly/test/integration/elytron/ejb/DefaultElytronEjbSecurityDomainTestCase.java b/testsuite/integration/elytron/src/test/java/org/wildfly/test/integration/elytron/ejb/DefaultElytronEjbSecurityDomainTestCase.java
index dee5422a40..48d077595d 100644
--- a/testsuite/integration/elytron/src/test/java/org/wildfly/test/integration/elytron/ejb/DefaultElytronEjbSecurityDomainTestCase.java
+++ b/testsuite/integration/elytron/src/test/java/org/wildfly/test/integration/elytron/ejb/DefaultElytronEjbSecurityDomainTestCase.java
@@ -79,7 +79,7 @@ public class DefaultElytronEjbSecurityDomainTestCase {
.addAsResource(currentPackage, "users.properties", "users.properties")
.addAsResource(currentPackage, "roles.properties", "roles.properties")
.addAsManifestResource(currentPackage, "jboss-ejb3.xml", "jboss-ejb3.xml")
- .addAsManifestResource(createPermissionsXmlAsset(new ElytronPermission("getSecurityDomain")), "permissions.xml");
+ .addAsManifestResource(createPermissionsXmlAsset(new ElytronPermission("getSecurityDomain"), new ElytronPermission("authenticate")), "permissions.xml");
}
{noformat}
[1] https://ci.wildfly.org/viewLog.html?buildId=128138&buildTypeId=WF_MasterS...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11349) Tests in org.jboss.as.test.clustering.cluster fails with security manager
by Martin Choma (Jira)
Martin Choma created WFLY-11349:
-----------------------------------
Summary: Tests in org.jboss.as.test.clustering.cluster fails with security manager
Key: WFLY-11349
URL: https://issues.jboss.org/browse/WFLY-11349
Project: WildFly
Issue Type: Bug
Components: Test Suite
Affects Versions: 14.0.0.Final
Reporter: Martin Choma
{noformat}
org.jboss.as.test.clustering.cluster.cdi (1)
CdiFailoverTestCase.test
org.jboss.as.test.clustering.cluster.jsf (2)
JSFFailoverTestCase.testGracefulSimpleFailover
JSFFailoverTestCase.testGracefulUndeployFailover
org.jboss.as.test.clustering.cluster.provider (1)
ServiceProviderRegistrationTestCase.test
org.jboss.as.test.clustering.cluster.singleton (4)
SingletonBackupServiceTestCase.testSingletonService
SingletonDeploymentDescriptorTestCase.test
SingletonDeploymentJBossAllTestCase.test
SingletonPartitionTestCase.testSingletonService
org.jboss.as.test.clustering.cluster.xsite (1)
XSiteSimpleTestCase.test
{noformat}
Seems to me doPrivileged block is missing in server code somewhere. There are errors like
{noformat}
Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "accessClassInPackage.sun.reflect")" in code source "(vfs:/content/CdiFailoverTestCase.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.CdiFailoverTestCase.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.lang.SecurityManager.checkPackageAccess(SecurityManager.java:1564)
at org.wildfly.security.manager.WildFlySecurityManager.checkPackageAccess(WildFlySecurityManager.java:490)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:318)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at org.jboss.modules.JDKSpecific.getSystemClass(JDKSpecific.java:180)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:395)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:310)
Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission \"(\"java.lang.RuntimePermission\" \"accessDeclaredMembers\")\" in code source \"(vfs:/content/XSiteSimpleTestCase.war/WEB-INF/classes <no signer certificates>)\" of \"ModuleClassLoader for Module \"deployment.XSiteSimpleTestCase.war\" from Service Module Loader\")"}}}}
Caused by: java.lang.ExceptionInInitializerError
at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1274)
{noformat}
[1] https://ci.wildfly.org/viewLog.html?buildId=128138&buildTypeId=WF_MasterS...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months