[JBoss JIRA] (WFLY-11512) Remove test workaround for CDI-727
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-11512?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-11512:
----------------------------------
Description:
Test {{EntityListenerBeanManagerInjectionTestCase}} used to fail with security manager due to CDI-727. However, a workaround has been applied to the test with WFLY-10125 - which seems wrong - the test should rather have been @ Ignored when running with security manager.
However, the original issue was already fixed with the component upgrade WFLY-10740 however the workaround has been kept in place which can mask further issues.
{{cd testsuite/integration/basic}}
{{mvn clean test -Dtest=EntityListenerBeanManagerInjectionTestCase -Dsecurity.manager}}
was:
Test {{EntityListenerBeanManagerInjectionTestCase}} used to fail with security manager due to CDI-727. However, a workaround has been applied to the test with WFLY-10125 - which seems wrong - the test should rather have been @ Ignored when running with security manager.
However, the original issue was already fixed with the component upgrade WFLY-10740 however the workaround has been kept in place which can mask further issues.
> Remove test workaround for CDI-727
> ----------------------------------
>
> Key: WFLY-11512
> URL: https://issues.jboss.org/browse/WFLY-11512
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 15.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Matej Novotny
> Priority: Major
> Fix For: 16.0.0.Beta1
>
>
> Test {{EntityListenerBeanManagerInjectionTestCase}} used to fail with security manager due to CDI-727. However, a workaround has been applied to the test with WFLY-10125 - which seems wrong - the test should rather have been @ Ignored when running with security manager.
> However, the original issue was already fixed with the component upgrade WFLY-10740 however the workaround has been kept in place which can mask further issues.
> {{cd testsuite/integration/basic}}
> {{mvn clean test -Dtest=EntityListenerBeanManagerInjectionTestCase -Dsecurity.manager}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11512) Remove test workaround for CDI-727
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-11512?page=com.atlassian.jira.plugin... ]
Radoslav Husar reassigned WFLY-11512:
-------------------------------------
Assignee: Radoslav Husar (was: Matej Novotny)
> Remove test workaround for CDI-727
> ----------------------------------
>
> Key: WFLY-11512
> URL: https://issues.jboss.org/browse/WFLY-11512
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 15.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: 16.0.0.Beta1
>
>
> Test {{EntityListenerBeanManagerInjectionTestCase}} used to fail with security manager due to CDI-727. However, a workaround has been applied to the test with WFLY-10125 - which seems wrong - the test should rather have been @ Ignored when running with security manager.
> However, the original issue was already fixed with the component upgrade WFLY-10740 however the workaround has been kept in place which can mask further issues.
> {{cd testsuite/integration/basic}}
> {{mvn clean test -Dtest=EntityListenerBeanManagerInjectionTestCase -Dsecurity.manager}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11512) Remove test workaround for CDI-727
by Radoslav Husar (Jira)
Radoslav Husar created WFLY-11512:
-------------------------------------
Summary: Remove test workaround for CDI-727
Key: WFLY-11512
URL: https://issues.jboss.org/browse/WFLY-11512
Project: WildFly
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 15.0.0.Final
Reporter: Radoslav Husar
Assignee: Matej Novotny
Fix For: 16.0.0.Beta1
Test {{EntityListenerBeanManagerInjectionTestCase}} used to fail with security manager due to CDI-727. However, a workaround has been applied to the test with WFLY-10125 - which seems wrong - the test should rather have been @ Ignored when running with security manager.
However, the original issue was already fixed with the component upgrade WFLY-10740 however the workaround has been kept in place which can mask further issues.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11510) EarOpenTracingWithWeldProbeTestCase fails with node0/1 set
by Ondrej Kotek (Jira)
[ https://issues.jboss.org/browse/WFLY-11510?page=com.atlassian.jira.plugin... ]
Ondrej Kotek reassigned WFLY-11510:
-----------------------------------
Assignee: Matej Novotny
> EarOpenTracingWithWeldProbeTestCase fails with node0/1 set
> ----------------------------------------------------------
>
> Key: WFLY-11510
> URL: https://issues.jboss.org/browse/WFLY-11510
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing, Test Suite
> Affects Versions: 16.0.0.Beta1
> Reporter: Ondrej Kotek
> Assignee: Matej Novotny
> Priority: Major
>
> {{org.jboss.as.test.integration.microprofile.opentracing.EarOpenTracingWithWeldProbeTestCase}} fails with {{node0}} and {{node1}} set:
> {noformat}
> WARN [org.jboss.weld.probe.Probe] (default task-1) PROBE-000017: Access to /ServiceOne/service-endpoint/app denied for <my IP>
> WARN [org.jboss.weld.probe.Probe] (default task-1) PROBE-000017: Access to /ServiceOne/service-endpoint/app denied for <my IP>
> ...
> java.lang.AssertionError: expected:<200> but was:<403>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at org.jboss.as.test.integration.microprofile.opentracing.AbstractEarOpenTracingTestCase.testHttpInvokation(AbstractEarOpenTracingTestCase.java:67)
> at org.jboss.as.test.integration.microprofile.opentracing.AbstractEarOpenTracingTestCase.testEarServicesUseDifferentTracersAfterReload(AbstractEarOpenTracingTestCase.java:59)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ...
> {noformat}
> Maybe access from remote IP addresses is blocked in development mode.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11500) Some web clustering tests fail with security manager
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-11500?page=com.atlassian.jira.plugin... ]
Radoslav Husar commented on WFLY-11500:
---------------------------------------
Will need Infinispan 9.4.5.Final upgrade, opened WFLY-11511.
> Some web clustering tests fail with security manager
> ----------------------------------------------------
>
> Key: WFLY-11500
> URL: https://issues.jboss.org/browse/WFLY-11500
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Test Suite
> Affects Versions: No Release
> Reporter: Ondrej Kotek
> Assignee: Radoslav Husar
> Priority: Major
>
> Five web clustering tests fail with security manager due to missing permissions:
> {noformat}
> ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ConcurrentFineWebFailoverTestCase/simple: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "accessDeclaredMembers")" in code source "(vfs:/content/ConcurrentFineWebFailoverTestCase.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.ConcurrentFineWebFailoverTestCase.war" from Service Module Loader")
> at org.wildfly.security.elytron-private@1.7.0.Final//org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:294)
> at org.wildfly.security.elytron-private@1.7.0.Final//org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:191)
> at java.base/java.lang.Class.checkMemberAccess(Class.java:2848)
> at java.base/java.lang.Class.getDeclaredMethod(Class.java:2472)
> at org.infinispan.commons@9.4.4.Final//org.infinispan.commons.util.ReflectionUtil.findMethod(ReflectionUtil.java:102)
> at org.infinispan@9.4.4.Final//org.infinispan.factories.components.ComponentMetadataRepo.initInjectionMethods(ComponentMetadataRepo.java:219)
> at org.infinispan@9.4.4.Final//org.infinispan.factories.components.ComponentMetadataRepo.initMetadata(ComponentMetadataRepo.java:129)
> at org.infinispan@9.4.4.Final//org.infinispan.factories.components.ComponentMetadataRepo.getComponentMetadata(ComponentMetadataRepo.java:119)
> at org.infinispan@9.4.4.Final//org.infinispan.factories.impl.BasicComponentRegistryImpl.wireDependencies(BasicComponentRegistryImpl.java:189)
> at org.infinispan@9.4.4.Final//org.infinispan.factories.AbstractComponentRegistry.wireDependencies(AbstractComponentRegistry.java:102)
> at org.infinispan(a)9.4.4.Final//org.infinispan.commands.write.ComputeCommand.<init>(ComputeCommand.java:51)
> at org.infinispan@9.4.4.Final//org.infinispan.commands.CommandsFactoryImpl.buildComputeCommand(CommandsFactoryImpl.java:283)
> at org.infinispan@9.4.4.Final//org.infinispan.cache.impl.CacheImpl.computeInternal(CacheImpl.java:337)
> at org.infinispan@9.4.4.Final//org.infinispan.cache.impl.DecoratedCache.compute(DecoratedCache.java:710)
> at org.infinispan@9.4.4.Final//org.infinispan.cache.impl.DecoratedCache.compute(DecoratedCache.java:630)
> at org.infinispan@9.4.4.Final//org.infinispan.cache.impl.AbstractDelegatingCache.compute(AbstractDelegatingCache.java:393)
> at org.infinispan@9.4.4.Final//org.infinispan.cache.impl.EncoderCache.compute(EncoderCache.java:642)
> at org.infinispan@9.4.4.Final//org.infinispan.cache.impl.AbstractDelegatingCache.compute(AbstractDelegatingCache.java:393)
> at org.wildfly.clustering.web.infinispan@16.0.0.Beta1-SNAPSHOT//org.wildfly.clustering.web.infinispan.session.fine.FineSessionAttributes.setAttribute(FineSessionAttributes.java:94)
> at org.wildfly.clustering.web.undertow@16.0.0.Beta1-SNAPSHOT//org.wildfly.clustering.web.undertow.session.DistributableSession.setAttribute(DistributableSession.java:173)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.spec.HttpSessionImpl.setAttribute(HttpSessionImpl.java:169)
> at deployment.ConcurrentFineWebFailoverTestCase.war//org.jboss.as.test.clustering.single.web.SimpleServlet.doGet(SimpleServlet.java:73)
> at javax.servlet.api@1.0.0.Final//javax.servlet.http.HttpServlet.service(HttpServlet.java:686)
> at javax.servlet.api@1.0.0.Final//javax.servlet.http.HttpServlet.service(HttpServlet.java:791)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129)
> at io.opentracing.contrib.opentracing-jaxrs2//io.opentracing.contrib.jaxrs2.server.SpanFinishingFilter.doFilter(SpanFinishingFilter.java:55)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:68)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
> at org.wildfly.extension.undertow@16.0.0.Beta1-SNAPSHOT//org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.core@2.0.15.Final//io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
> at io.undertow.core@2.0.15.Final//io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.core@2.0.15.Final//io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.core@2.0.15.Final//io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
> at io.undertow.core@2.0.15.Final//io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
> at io.undertow.core@2.0.15.Final//io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> at io.undertow.core@2.0.15.Final//io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow@16.0.0.Beta1-SNAPSHOT//org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.core@2.0.15.Final//io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow@16.0.0.Beta1-SNAPSHOT//org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
> at io.undertow.core@2.0.15.Final//io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow@16.0.0.Beta1-SNAPSHOT//org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow@16.0.0.Beta1-SNAPSHOT//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at org.wildfly.extension.undertow@16.0.0.Beta1-SNAPSHOT//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at org.wildfly.extension.undertow@16.0.0.Beta1-SNAPSHOT//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at org.wildfly.extension.undertow@16.0.0.Beta1-SNAPSHOT//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.ServletInitialHandler$1$1.run(ServletInitialHandler.java:110)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at io.undertow.servlet@2.0.15.Final//io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:107)
> at io.undertow.core@2.0.15.Final//io.undertow.server.Connectors.executeRootHandler(Connectors.java:360)
> at io.undertow.core@2.0.15.Final//io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
> Affected test cases:
> * {{org.jboss.as.test.clustering.cluster.web.ConcurrentFineWebFailoverTestCase#test}}
> * {{org.jboss.as.test.clustering.cluster.web.FineWebFailoverTestCase#test}}
> * {{org.jboss.as.test.clustering.cluster.web.async.AsyncServletTestCase#test}}
> * {{org.jboss.as.test.clustering.cluster.web.expiration.FineSessionExpirationTestCase#test}}
> * {{org.jboss.as.test.clustering.cluster.web.passivation.FineSessionPassivationTestCase#test}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11510) EarOpenTracingWithWeldProbeTestCase fails with node0/1 set
by Ondrej Kotek (Jira)
Ondrej Kotek created WFLY-11510:
-----------------------------------
Summary: EarOpenTracingWithWeldProbeTestCase fails with node0/1 set
Key: WFLY-11510
URL: https://issues.jboss.org/browse/WFLY-11510
Project: WildFly
Issue Type: Bug
Components: MP OpenTracing, Test Suite
Affects Versions: 16.0.0.Beta1
Reporter: Ondrej Kotek
{{org.jboss.as.test.integration.microprofile.opentracing.EarOpenTracingWithWeldProbeTestCase}} fails with {{node0}} and {{node1}} set:
{noformat}
WARN [org.jboss.weld.probe.Probe] (default task-1) PROBE-000017: Access to /ServiceOne/service-endpoint/app denied for <my IP>
WARN [org.jboss.weld.probe.Probe] (default task-1) PROBE-000017: Access to /ServiceOne/service-endpoint/app denied for <my IP>
...
java.lang.AssertionError: expected:<200> but was:<403>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at org.jboss.as.test.integration.microprofile.opentracing.AbstractEarOpenTracingTestCase.testHttpInvokation(AbstractEarOpenTracingTestCase.java:67)
at org.jboss.as.test.integration.microprofile.opentracing.AbstractEarOpenTracingTestCase.testEarServicesUseDifferentTracersAfterReload(AbstractEarOpenTracingTestCase.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...
{noformat}
Maybe access from remote IP addresses is blocked in development mode.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (JGRP-2288) S3_PING: Under certain conditions, subclusters fail to merge after network partition
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2288?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2288:
--------------------------------
Unit test: FILE_PING_Test
> S3_PING: Under certain conditions, subclusters fail to merge after network partition
> ------------------------------------------------------------------------------------
>
> Key: JGRP-2288
> URL: https://issues.jboss.org/browse/JGRP-2288
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.15
> Reporter: Nick Sawadsky
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.0.17
>
>
> Repro steps:
> 1. Set up a cluster of four nodes, two on one machine (Host 1) and two on another (Host 2). Let's call the nodes A, B, C, and D.
> 2. Configure all 4 nodes with S3_PING as the discovery mechanism. Set remove_all_files_on_view_change to true.
> 3. Start up nodes in the order A, B, C, D.
> 4. In the S3 bucket, there should be a single file with all four nodes listed. Node A should be flagged as the coordinator. Ensure that the UUID for node B is larger than the UUID for node C, when compared as two's complement integers. If this is not the case, shut down all nodes and restart in order. Repeat until the desired relationship is achieved. Note that with two's complement, a UUID having a first hex digit of 8 or higher is treated as negative for comparison purposes. So, for example, a UUID starting with 'a' is less than a UUID starting with 'b' which is less than a UUID starting with '1'.
> 5. On Host 1, use iptables to block all traffic going to and coming from Host 2.
> sudo iptables -A INPUT -s <Host 2 IP addr> -j DROP
> sudo iptables -A OUTPUT -d <Host 2 IP addr> -j DROP
> 6. Allow a few minutes for the nodes to detect the network partition. Eventually you should see two files in the S3 bucket.
> 7. Using Ctrl-C, stop node A.
> 8. You should soon find only a single file in the bucket, containing a single entry for node B. This is a result of the remove_all_files_on_view_change setting on S3_PING, which we set to true to avoid accumulation of old files in the bucket.
> 9. Resolve the network partition:
> sudo iptables -F OUTPUT
> sudo iptables -F INPUT
> 10. You will find that, even after many minutes, the subclusters are not merged.
> I believe the reason why the subclusters are never merged is as follows:
> - MERGE3 on nodes B, C and D uses S3_PING to find members to send INFO messages to. Each one finds only node B in the discovery file. As a result, only node B's view consistency checker has anything to work with.
> - On node B, the consistency checker can see that there are two coordinators, B and C. However, node C has a lower UUID, so node B defers to it to perform the merge. Node C never performs the merge because, as mentioned above, it is not receiving any INFO messages.
> I this this problem would affect FILE_PING as well, and other protocols derived from FILE_PING. Looking at the latest 4.x code, it appears the problem still exists there.
> I think the crux of the issue is that the coordinator on Host 2 (node C) does not re-create its discovery file after it is deleted by node B. Would it be reasonable for FILE_PING.findMembers() to create the discovery file if the node is a coordinator and the file doesn't exist?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11458) Timed - difference between Prometheus and JSON format
by Bartosz Baranowski (Jira)
[ https://issues.jboss.org/browse/WFLY-11458?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski commented on WFLY-11458:
-------------------------------------------
Difference comes from : https://github.com/smallrye/smallrye-metrics/blob/master/implementation/s...
{quote}
PrometheusUnit.scaleToBase(String, Double) line: 144
PrometheusExporter.writeValueLine(StringBuffer, MetricRegistry$Type, String, double, Metadata, Tag, boolean) line: 273
PrometheusExporter.writeValueLine(StringBuffer, MetricRegistry$Type, String, double, Metadata, Tag) line: 246
PrometheusExporter.writeValueLine(StringBuffer, MetricRegistry$Type, String, double, Metadata) line: 242
PrometheusExporter.writeTypeAndValue(StringBuffer, MetricRegistry$Type, String, double, String, Metadata) line: 238
PrometheusExporter.writeMeterRateValues(StringBuffer, MetricRegistry$Type, Metered, Metadata) line: 232
PrometheusExporter.writeTimerValues(StringBuffer, MetricRegistry$Type, TimerImpl, Metadata) line: 177
PrometheusExporter.exposeEntries(Type, StringBuffer, MetricRegistry, Map<String,Metric>) line: 154
PrometheusExporter.exportOneMetric(MetricRegistry$Type, String) line: 105
MetricsRequestHandler.handleRequest(String, String, Stream<String>, Responder) line: 100
MetricsContextService$1.handleRequest(HttpServerExchange) line: 93
ServerErrorReadinessHandler(RealmReadinessHandler).handleRequest(HttpServerExchange) line: 51
ServerErrorReadinessHandler.handleRequest(HttpServerExchange) line: 35
PathHandler.handleRequest(HttpServerExchange) line: 94
ChannelUpgradeHandler.handleRequest(HttpServerExchange) line: 211
CacheHandler.handleRequest(HttpServerExchange) line: 92
SimpleErrorPageHandler.handleRequest(HttpServerExchange) line: 78
CanonicalPathHandler.handleRequest(HttpServerExchange) line: 49
ManagementHttpRequestHandler.handleRequest(HttpServerExchange) line: 57
CorsHttpHandler.handleRequest(HttpServerExchange) line: 75
ManagementHttpServer$UpgradeFixHandler.handleRequest(HttpServerExchange) line: 662
Connectors.executeRootHandler(HttpHandler, HttpServerExchange) line: 360
HttpReadListener.handleEventWithNoRunningRequest(ConduitStreamSourceChannel) line: 255
HttpReadListener.handleEvent(ConduitStreamSourceChannel) line: 136
HttpOpenListener.handleEvent(StreamConnection, PooledByteBuffer) line: 162
HttpOpenListener.handleEvent(StreamConnection) line: 100
HttpOpenListener.handleEvent(Channel) line: 57
ChannelListeners.invokeChannelListener(T, ChannelListener<? super T>) line: 92
ChannelListeners$10.handleEvent(AcceptingChannel<C>) line: 291
ChannelListeners$10.handleEvent(Channel) line: 286
ChannelListeners.invokeChannelListener(T, ChannelListener<? super T>) line: 92
QueuedNioTcpServer$1.run() line: 131
WorkerThread.safeRun(Runnable) line: 612
WorkerThread.run() line: 479
{quote}
Im trying to fiure out the rationale behind this. JsonExporter writes just raw value( as does OpenLiberty for every call): https://github.com/smallrye/smallrye-metrics/blob/master/implementation/s...
> Timed - difference between Prometheus and JSON format
> -----------------------------------------------------
>
> Key: WFLY-11458
> URL: https://issues.jboss.org/browse/WFLY-11458
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Affects Versions: 15.0.0.Final
> Reporter: Rostislav Svoboda
> Assignee: Bartosz Baranowski
> Priority: Critical
>
> There are differences in reported results between Prometheus and JSON format.
> When using the same deployment with OpenLiberty there are no differences in reported results between Prometheus and JSON format.
> https://github.com/smallrye/smallrye-metrics/issues/40
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months