November 2018 - jboss-jira - Jboss List Archives

[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, 7 months

1
0
0 / 0

[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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2697) [DMN Designer] Improve readability of node labels

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2697?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2697: ------------------------------------- +1 for removing _font border_. > [DMN Designer] Improve readability of node labels > ------------------------------------------------- > > Key: DROOLS-2697 > URL: https://issues.jboss.org/browse/DROOLS-2697 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Guilherme Carreiro > Assignee: Daniel José dos Santos > Priority: Major > > Node names are bold text without background rectangle and hence _merge_ into the node SVG. It'd be nicer to change font to regular and provide a (white) background rectangle to improve readability. See https://github.com/kiegroup/kie-wb-common/pull/1929#pullrequestreview-133... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[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, 7 months

1
0
0 / 0

[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, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11401) Upgrade Infinispan to 9.4.3.Final

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-11401?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-11401: ------------------------------------- That said, I'll continue to monitor these tests. Worst case - if we find any more holes in Infinispan's transaction table graceful shutdown logic we can restore a more permissive version of the distributed session manager lifecycle locking that was removed in https://github.com/wildfly/wildfly/commit/88f0cd5bd076ebbbf6fa501c8afa294... We may need to anyway, as our clean undeploy tests have been a mess since this was dropped. > Upgrade Infinispan to 9.4.3.Final > --------------------------------- > > Key: WFLY-11401 > URL: https://issues.jboss.org/browse/WFLY-11401 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 15.0.0.Beta1 > Reporter: Tomas Hofman > Assignee: Paul Ferraro > Priority: Critical > Fix For: 15.0.0.CR1 > > > https://issues.jboss.org/projects/ISPN/versions/12339982 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11401) Upgrade Infinispan to 9.4.3.Final

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-11401?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-11401: ------------------------------------- The stack traces indicates that Infinispan transaction commit defers to a synchronization, which should no longer be the case following https://github.com/wildfly/wildfly/commit/fdfdbad816c7a76b20b2569523ef058... > Upgrade Infinispan to 9.4.3.Final > --------------------------------- > > Key: WFLY-11401 > URL: https://issues.jboss.org/browse/WFLY-11401 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 15.0.0.Beta1 > Reporter: Tomas Hofman > Assignee: Paul Ferraro > Priority: Critical > Fix For: 15.0.0.CR1 > > > https://issues.jboss.org/projects/ISPN/versions/12339982 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11401) Upgrade Infinispan to 9.4.3.Final

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11401?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-11401: ----------------------------------------- I think the CI job I linked was run after that commit was in master, as Kabir merged that commit 9 hours ago. But I'll be optimistic. :) > Upgrade Infinispan to 9.4.3.Final > --------------------------------- > > Key: WFLY-11401 > URL: https://issues.jboss.org/browse/WFLY-11401 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 15.0.0.Beta1 > Reporter: Tomas Hofman > Assignee: Paul Ferraro > Priority: Critical > Fix For: 15.0.0.CR1 > > > https://issues.jboss.org/projects/ISPN/versions/12339982 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11322) RemoteStatefulEJBConcurrentFailoverTestCase is unreliable

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11322?page=com.atlassian.jira.plugin... ] James Perkins resolved WFLY-11322. ---------------------------------- Fix Version/s: 15.0.0.CR1 Resolution: Done > RemoteStatefulEJBConcurrentFailoverTestCase is unreliable > --------------------------------------------------------- > > Key: WFLY-11322 > URL: https://issues.jboss.org/browse/WFLY-11322 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Brian Stansberry > Assignee: Radoslav Husar > Priority: Major > Fix For: 15.0.0.CR1 > > > Test is failing regularly. > https://ci.wildfly.org/project.html?projectId=WF&buildTypeId=&tab=testDet... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11384) StatefulFailoverTestCase fails intermittently

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11384?page=com.atlassian.jira.plugin... ] James Perkins resolved WFLY-11384. ---------------------------------- Fix Version/s: 15.0.0.CR1 Resolution: Done > StatefulFailoverTestCase fails intermittently > --------------------------------------------- > > Key: WFLY-11384 > URL: https://issues.jboss.org/browse/WFLY-11384 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 15.0.0.Beta1 > Environment: Any > Reporter: Ondrej Kotek > Assignee: Radoslav Husar > Priority: Major > Fix For: 15.0.0.CR1 > > > The tests of {{org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase}} occasionally fail, for example: > {noformat} > [ERROR] Failures: > [ERROR] StatefulFailoverTestCase.jmsConnectionFactoryFailover:166->failover:193->queryCount:315 expected:<200> but was:<500> > [ERROR] StatefulFailoverTestCase.nestedBeanFailover:286->queryCount:315 expected:<200> but was:<500> > [ERROR] StatefulFailoverTestCase.noFailover:117 expected:<1> but was:<3> > {noformat} > or > {noformat} > [ERROR] Failures: > [ERROR] StatefulFailoverTestCase.nestedBeanFailover:286->queryCount:315 expected:<200> but was:<500> > [ERROR] StatefulFailoverTestCase.noFailover:117->queryCount:315 expected:<200> but was:<500> > [ERROR] StatefulFailoverTestCase.simpleFailover:145->failover:193->queryCount:315 expected:<200> but was:<500> > {noformat} > connectionFactoryFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=-822829635945... > noFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=-574944609062... > jmsConnectionFactoryFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=3564603678560... > simpleFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=4824753507849... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2018