January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12941) Microprofile count metrics does not increase in wildfly17

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12941?page=com.atlassian.jira.plugi... ] Bartosz Baranowski resolved WFLY-12941. --------------------------------------- Fix Version/s: 18.0.0.Final Assignee: Bartosz Baranowski (was: Jeff Mesnil) Resolution: Out of Date Resolving based on Reporters last comment - fixed in 18. > Microprofile count metrics does not increase in wildfly17 > ---------------------------------------------------------- > > Key: WFLY-12941 > URL: https://issues.redhat.com/browse/WFLY-12941 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: alireza alallah > Assignee: Bartosz Baranowski > Priority: Major > Fix For: 18.0.0.Final > > > for example > @Path("/") > public class RESTEndpoints { > > @GET > @Path("/hello") > @Counted(name"total_count",absolute = true) > public String hello(@DefaultValue("my friend!") @QueryParam("name") String name) { > return "Hello "+name; > > } > > } > Now in http://localhost:9990/metrics *total_count* metric does not increase after invoke endpoint. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12941) Microprofile count metrics does not increase in wildfly17

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12941?page=com.atlassian.jira.plugi... ] Bartosz Baranowski commented on WFLY-12941: ------------------------------------------- [~alireza.alallah] - WFLY is rolling forward, there are no backport( AFAIR ) - so yes. > Microprofile count metrics does not increase in wildfly17 > ---------------------------------------------------------- > > Key: WFLY-12941 > URL: https://issues.redhat.com/browse/WFLY-12941 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: alireza alallah > Assignee: Jeff Mesnil > Priority: Major > > for example > @Path("/") > public class RESTEndpoints { > > @GET > @Path("/hello") > @Counted(name"total_count",absolute = true) > public String hello(@DefaultValue("my friend!") @QueryParam("name") String name) { > return "Hello "+name; > > } > > } > Now in http://localhost:9990/metrics *total_count* metric does not increase after invoke endpoint. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12968) SecurityDomainContextRealm is not caching passwords correctly

by Ricardo Martin Camarero (Jira)

Ricardo Martin Camarero created WFLY-12968: ---------------------------------------------- Summary: SecurityDomainContextRealm is not caching passwords correctly Key: WFLY-12968 URL: https://issues.redhat.com/browse/WFLY-12968 Project: WildFly Issue Type: Bug Components: Security Affects Versions: 18.0.1.Final Reporter: Ricardo Martin Camarero Assignee: Ricardo Martin Camarero The [SecurityDomainContextRealm|https://github.com/wildfly/wildfly/blob/18.0.1...] realm used in elytron mixed scenarios is not taken advantage of the cache if the underlying security-domain is configured with default cache ({{cache-type="default"}}). The problem is similar to what is commented in the [JAASIdentityManagerImpl|https://github.com/wildfly/wildfly/blob/18.0.1.Fi...], the evidence reset the password and then the cache is useless. The solution can also be cloning the password char[] before, this way the cache is OK and the array can be compared correctly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12088) JAR does not supported for deployment-overlays mechanism

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12088?page=com.atlassian.jira.plugi... ] Bartosz Baranowski reassigned WFLY-12088: ----------------------------------------- Assignee: Bartosz Baranowski (was: Richard Opalka) > JAR does not supported for deployment-overlays mechanism > -------------------------------------------------------- > > Key: WFLY-12088 > URL: https://issues.redhat.com/browse/WFLY-12088 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Affects Versions: 16.0.0.Final > Reporter: Vlad Filipp > Assignee: Bartosz Baranowski > Priority: Major > > When trying to make a link from an overlay to a JAR, classes from overlay libraries are not loaded for a linked JAR. > The situation is similar when creating a link to a JAR which is located inside EAR. > Should overlay deployment mechanism be supported for JARs? > Example standalone.xml: > {code:java} > <deployment-overlays> > ... > <deployment-overlay name="my-overlay-n1"> > <content ...> > <deployment name="my-jar-inside-ear-use-overlays-libs.jar"/> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12088) JAR does not supported for deployment-overlays mechanism

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12088?page=com.atlassian.jira.plugi... ] Bartosz Baranowski edited comment on WFLY-12088 at 1/15/20 1:53 AM: -------------------------------------------------------------------- Hi [~vladimirfrankov] could you please attach reproducer or full description with steps to trigger failure? was (Author: baranowb): Hi [~vladimirfrankov] could you please attach reproducer or steps to trigger failure? > JAR does not supported for deployment-overlays mechanism > -------------------------------------------------------- > > Key: WFLY-12088 > URL: https://issues.redhat.com/browse/WFLY-12088 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Affects Versions: 16.0.0.Final > Reporter: Vlad Filipp > Assignee: Richard Opalka > Priority: Major > > When trying to make a link from an overlay to a JAR, classes from overlay libraries are not loaded for a linked JAR. > The situation is similar when creating a link to a JAR which is located inside EAR. > Should overlay deployment mechanism be supported for JARs? > Example standalone.xml: > {code:java} > <deployment-overlays> > ... > <deployment-overlay name="my-overlay-n1"> > <content ...> > <deployment name="my-jar-inside-ear-use-overlays-libs.jar"/> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12088) JAR does not supported for deployment-overlays mechanism

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12088?page=com.atlassian.jira.plugi... ] Bartosz Baranowski commented on WFLY-12088: ------------------------------------------- Hi [~vladimirfrankov] could you please attach reproducer or steps to trigger failure? > JAR does not supported for deployment-overlays mechanism > -------------------------------------------------------- > > Key: WFLY-12088 > URL: https://issues.redhat.com/browse/WFLY-12088 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Affects Versions: 16.0.0.Final > Reporter: Vlad Filipp > Assignee: Richard Opalka > Priority: Major > > When trying to make a link from an overlay to a JAR, classes from overlay libraries are not loaded for a linked JAR. > The situation is similar when creating a link to a JAR which is located inside EAR. > Should overlay deployment mechanism be supported for JARs? > Example standalone.xml: > {code:java} > <deployment-overlays> > ... > <deployment-overlay name="my-overlay-n1"> > <content ...> > <deployment name="my-jar-inside-ear-use-overlays-libs.jar"/> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12966) Upgrade Hibernate ORM from 5.3.14 to 5.3.15

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12966?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFLY-12966: --------------------------------- Labels: downstream_dependency (was: ) > Upgrade Hibernate ORM from 5.3.14 to 5.3.15 > ------------------------------------------- > > Key: WFLY-12966 > URL: https://issues.redhat.com/browse/WFLY-12966 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Gail Badner > Assignee: Gail Badner > Priority: Major > Labels: downstream_dependency > Fix For: 19.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12909) Fix license names for org.hdrhistogram:HdrHistogram licenses

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-12909?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-12909: ---------------------------------- Affects Version/s: No Release > Fix license names for org.hdrhistogram:HdrHistogram licenses > ------------------------------------------------------------- > > Key: WFLY-12909 > URL: https://issues.redhat.com/browse/WFLY-12909 > Project: WildFly > Issue Type: Task > Components: MP Fault Tolerance > Affects Versions: No Release > Reporter: James Perkins > Assignee: Radoslav Husar > Priority: Blocker > Fix For: 19.0.0.Beta1 > > > This isn't a blocker for beta, but should be for 19.0.0.Final as the generated license names need to match a license name in https://spdx.org/licenses/. > On the [PR|https://github.com/wildfly/wildfly/pull/12800/files/9c843d1a0e00172b00...] to introduce fault tolerance doesn't have quite the right license text for {{org.hdrhistogram:HdrHistogram}}. Looking at the [license file|https://github.com/HdrHistogram/HdrHistogram/blob/master/LICENSE.txt] we just need to determine which license name should be used as both licenses have multiple names. > One other minor note. The order the licenses are listed in the {{full-feature-pack-licenses.xml}} for this dependency may need to be swapped. I _believe_ these need to be in alphabetical order. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4930) [DMN Designer] Remove UUID from Alerts panel validation messages

by Roger Martinez (Jira)

[ https://issues.redhat.com/browse/DROOLS-4930?page=com.atlassian.jira.plug... ] Roger Martinez commented on DROOLS-4930: ---------------------------------------- Hey [~jomarko], yes I think so, although IMO there a a few gaps to consider yet. Think that the idea is having some String that references the element in the output logs, so: * if some name is present for the element, probably no need for UUID * But in case a node has no name, for example just when adding a gateway, which reference you'll use on the logs? There is only UUID available I would say * Also, it can be a point where names are duplicated accross elements, so that may be confusing also just to display the name where there exist several related nodes, right? So I think the solution, whatever it is, may apply to both DMN and BPMN, but it's not yet clear for me how to behave... Thx! > [DMN Designer] Remove UUID from Alerts panel validation messages > ----------------------------------------------------------------- > > Key: DROOLS-4930 > URL: https://issues.redhat.com/browse/DROOLS-4930 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Validation of a DMN diagram can lead to messages being shown in the Alerts Panel. > Stunner is appending the UUID to the message. See [CoreTranslationMessages.getElementValidationMessage()|https://github.com/...] > [~tirelli] has requested their removal. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12957) MP Fault tolerance tests are failing on Ubuntu

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-12957?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-12957: ---------------------------------- Fix Version/s: 19.0.0.Beta1 > MP Fault tolerance tests are failing on Ubuntu > ---------------------------------------------- > > Key: WFLY-12957 > URL: https://issues.redhat.com/browse/WFLY-12957 > Project: WildFly > Issue Type: Bug > Components: MP Fault Tolerance, Test Suite > Affects Versions: No Release > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 19.0.0.Beta1 > > > Environment variables with dots in their name are not supported on Ubuntu making the fault tolerance tests fail. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 January 2020