May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13445) Upgrade RESTEasy to 3.12.0.Final

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-13445?page=com.atlassian.jira.plugi... ] Ronald Sigal updated WFLY-13445: -------------------------------- Description: Upgrade from 3.11.2.Final to 3.12.0.Final (was: Upgrade from 3.6.3.Final to 3.6.3.SP1 in which all references to repository are made with https.) Fix Version/s: 20.0.0.Beta1 (was: 17.0.0.Final) (was: 17.0.0.Beta1) Affects Version/s: (was: 16.0.0.Final) > Upgrade RESTEasy to 3.12.0.Final > -------------------------------- > > Key: WFLY-13445 > URL: https://issues.redhat.com/browse/WFLY-13445 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Ronald Sigal > Assignee: Ronald Sigal > Priority: Major > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > > Upgrade from 3.11.2.Final to 3.12.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13445) Upgrade RESTEasy to 3.12.0.Final

by Ronald Sigal (Jira)

Ronald Sigal created WFLY-13445: ----------------------------------- Summary: Upgrade RESTEasy to 3.12.0.Final Key: WFLY-13445 URL: https://issues.redhat.com/browse/WFLY-13445 Project: WildFly Issue Type: Component Upgrade Components: REST Affects Versions: 16.0.0.Final Reporter: Ronald Sigal Assignee: Ronald Sigal Fix For: 17.0.0.Beta1, 17.0.0.Final Upgrade from 3.6.3.Final to 3.6.3.SP1 in which all references to repository are made with https. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12835) HealthChecks in subdeployments are not registered

by charles ghislain (Jira)

[ https://issues.redhat.com/browse/WFLY-12835?page=com.atlassian.jira.plugi... ] charles ghislain edited comment on WFLY-12835 at 5/8/20 10:48 AM: ------------------------------------------------------------------ Seeing this still classified as a feature request, I should point out that application health checks packaged in subdeployment archives were correctly discovered on wildfly 16. was (Author: cghislai): Seeing this still classified as a feature request, I should point out that application health checks packaged in subdeployment archives where correctly discovered on wildfly 16. > HealthChecks in subdeployments are not registered > ------------------------------------------------- > > Key: WFLY-12835 > URL: https://issues.redhat.com/browse/WFLY-12835 > Project: WildFly > Issue Type: Feature Request > Components: MP Health > Affects Versions: 18.0.1.Final > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Critical > > After EAR is deployed HealthChecks are not registered and not exposed under _/health_ endpoint. > EAR contains one WAR and one JAR. Both of them contains HealthChecks. > Test source: https://github.com/istraka/eap-microprofile-test-suite/blob/mp-health/mic... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12835) HealthChecks in subdeployments are not registered

by charles ghislain (Jira)

[ https://issues.redhat.com/browse/WFLY-12835?page=com.atlassian.jira.plugi... ] charles ghislain commented on WFLY-12835: ----------------------------------------- Seeing this still classified as a feature request, I should point out that application health checks packaged in subdeployment archives where correctly discovered on wildfly 16. > HealthChecks in subdeployments are not registered > ------------------------------------------------- > > Key: WFLY-12835 > URL: https://issues.redhat.com/browse/WFLY-12835 > Project: WildFly > Issue Type: Feature Request > Components: MP Health > Affects Versions: 18.0.1.Final > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Critical > > After EAR is deployed HealthChecks are not registered and not exposed under _/health_ endpoint. > EAR contains one WAR and one JAR. Both of them contains HealthChecks. > Test source: https://github.com/istraka/eap-microprofile-test-suite/blob/mp-health/mic... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12835) HealthChecks in subdeployments are not registered

by charles ghislain (Jira)

[ https://issues.redhat.com/browse/WFLY-12835?page=com.atlassian.jira.plugi... ] charles ghislain edited comment on WFLY-12835 at 5/8/20 10:42 AM: ------------------------------------------------------------------ This seems related to WFLY-12811 and commit https://github.com/wildfly/wildfly/commit/4f3bc4754216136e19470bdd3a84124.... The [DeploymentProcessor|https://github.com/wildfly/wildfly/blob/5bad8de7386fe...] registers a CDIExtension instance for each deployment (sub)module, but only the last one is preserved as only one instance of each extension type may be registered ([WeldPortableExtensions javadoc|https://github.com/wildfly/wildfly/blob/64debb7134598bebb03fccf55...]). However, by only registering the extension on parent modules (ei skipping wars when inside ears), the config property is not injected as reported in WFLY-12811. The real issue seems to be in the [AfterDeploymentValidation listener|https://github.com/wildfly/wildfly/blob/8b321779c6bc17a44f699705...], as the injected BeanManager does not resolve healthchecks in the war inside an ear. Strangley, `InitialContext.doLookup("java:comp/BeanManager")` throws a NameNotFoundException there, while `CDI.current().getBeanManager()` returns a beanManager suitable to resolve all healthchecks. I edited [MicroProfileHealthTestBase|https://github.com/cghislai/wildfly/blob/mp-he...] to deploy the war in an ear, and modified the cdi extension as well as the deployment processor to only register a single extension for the parent module, and use CDI.current where JNDI lookup would fail. Using that change, test fails because of "Required property org.wildfly.test.integration.microprofile.health.MyProbe.propertyConfiguredByTheDeployment not found", but the probes seem correctly resolved. was (Author: cghislai): This seems related to WFLY-12811 and commit https://github.com/wildfly/wildfly/commit/4f3bc4754216136e19470bdd3a84124.... The [DeploymentProcessor|https://github.com/wildfly/wildfly/blob/5bad8de7386fe...] registers a CDIExtension instance for each deployment (sub)module, but only the last one is preserved as only one instance of each extension type may be registered ([WeldPortableExtensions javadoc|https://github.com/wildfly/wildfly/blob/64debb7134598bebb03fccf55...]). However, by only registering the extension on parent modules (ei skipping wars when inside ears), the config property is not injected as reported in WFLY-12811. The real issue seems to be in the [AfterDeploymentValidation listener|https://github.com/wildfly/wildfly/blob/8b321779c6bc17a44f699705...], as the injected BeanManager does not resolve healthchecks in the war inside an ear. Strangley, `InitialContext.doLookup("java:comp/BeanManager")` throws a NameNotFoundException there, while `CDI.current().getBeanManager()` returns a beanManager suitable to resolve all healthchecks. I edited [MicroProfileHealthTestBase|https://github.com/cghislai/wildfly/blob/mp-he...] to deploy the war in an ear. Using that change, test fails because of "Required property org.wildfly.test.integration.microprofile.health.MyProbe.propertyConfiguredByTheDeployment not found", but the probes seem correctly resolved. > HealthChecks in subdeployments are not registered > ------------------------------------------------- > > Key: WFLY-12835 > URL: https://issues.redhat.com/browse/WFLY-12835 > Project: WildFly > Issue Type: Feature Request > Components: MP Health > Affects Versions: 18.0.1.Final > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Critical > > After EAR is deployed HealthChecks are not registered and not exposed under _/health_ endpoint. > EAR contains one WAR and one JAR. Both of them contains HealthChecks. > Test source: https://github.com/istraka/eap-microprofile-test-suite/blob/mp-health/mic... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12835) HealthChecks in subdeployments are not registered

by charles ghislain (Jira)

[ https://issues.redhat.com/browse/WFLY-12835?page=com.atlassian.jira.plugi... ] charles ghislain commented on WFLY-12835: ----------------------------------------- This seems related to WFLY-12811 and commit https://github.com/wildfly/wildfly/commit/4f3bc4754216136e19470bdd3a84124.... The [DeploymentProcessor|https://github.com/wildfly/wildfly/blob/5bad8de7386fe...] registers a CDIExtension instance for each deployment (sub)module, but only the last one is preserved as only one instance of each extension type may be registered ([WeldPortableExtensions javadoc|https://github.com/wildfly/wildfly/blob/64debb7134598bebb03fccf55...]). However, by only registering the extension on parent modules (ei skipping wars when inside ears), the config property is not injected as reported in WFLY-12811. The real issue seems to be in the [AfterDeploymentValidation listener|https://github.com/wildfly/wildfly/blob/8b321779c6bc17a44f699705...], as the injected BeanManager does not resolve healthchecks in the war inside an ear. Strangley, `InitialContext.doLookup("java:comp/BeanManager")` throws a NameNotFoundException there, while `CDI.current().getBeanManager()` returns a beanManager suitable to resolve all healthchecks. I edited [MicroProfileHealthTestBase|https://github.com/cghislai/wildfly/blob/mp-he...] to deploy the war in an ear. Using that change, test fails because of "Required property org.wildfly.test.integration.microprofile.health.MyProbe.propertyConfiguredByTheDeployment not found", but the probes seem correctly resolved. > HealthChecks in subdeployments are not registered > ------------------------------------------------- > > Key: WFLY-12835 > URL: https://issues.redhat.com/browse/WFLY-12835 > Project: WildFly > Issue Type: Feature Request > Components: MP Health > Affects Versions: 18.0.1.Final > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Critical > > After EAR is deployed HealthChecks are not registered and not exposed under _/health_ endpoint. > EAR contains one WAR and one JAR. Both of them contains HealthChecks. > Test source: https://github.com/istraka/eap-microprofile-test-suite/blob/mp-health/mic... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5820) Rename urn:delivery-active schema namespace to urn:delivery

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-5820?page=com.atlassian.jira.plugin... ] Ranabir Chakraborty commented on WFLY-5820: ------------------------------------------- [~pferraro] Can you explain a bit more about this issue? > Rename urn:delivery-active schema namespace to urn:delivery > ----------------------------------------------------------- > > Key: WFLY-5820 > URL: https://issues.redhat.com/browse/WFLY-5820 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.CR4 > Reporter: Paul Ferraro > Assignee: Cheng Fang > Priority: Major > > This schema is no longer just used for the delivery active flag, but also for associating a delivery group. The current schema name is confusing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2442) Performance tests

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2442?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2442: --------------------------- Fix Version/s: 5.0.0.Beta2 (was: 5.0.0.Beta1) > Performance tests > ----------------- > > Key: JGRP-2442 > URL: https://issues.redhat.com/browse/JGRP-2442 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Beta2 > > > Run UPerf/MPerf before releasing 5.0.0.Final. > Performance should be slightly better due to reduced memory pressure (LongMessage, EmptyMessage, one less memory allocation)... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2475) RpcDispatcher: use ObjectMessage

by Bela Ban (Jira)

Bela Ban created JGRP-2475: ------------------------------ Summary: RpcDispatcher: use ObjectMessage Key: JGRP-2475 URL: https://issues.redhat.com/browse/JGRP-2475 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0.0.Beta2 When invoking RPCs, {{RpcDispatcher}} converts the {{MethodCall}} used into a byte array and passes that to a {{BytesMessage}} that's then sent down to the transport. This is inefficient, as an unneeded byte array allocation is done, both when an RPC request is sent and when the response is sent. Instead of doing eager marshalling of {{MethodCall}} into a byte array, pass the {{MethodCall}} to an {{ObjectMessage}}, which marshalls the latter directly to the output stream of the transport at send time. This eliminates 2 memory allocations per RPC round-trip (on a sync RPC). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5284) MVELTest.testTypeCoercionLongDivByInt fails with IBM JDK 8

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5284?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-5284: ------------------------------------------- Fixed by https://github.com/mvel/mvel/pull/233/commits/d9d0a93a0a25514b6e777ebb9b3... Drools will need to consume mvel 2.4.8.Final or later. > MVELTest.testTypeCoercionLongDivByInt fails with IBM JDK 8 > ---------------------------------------------------------- > > Key: DROOLS-5284 > URL: https://issues.redhat.com/browse/DROOLS-5284 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.36.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > MVELTest.testTypeCoercionLongDivByInt fails with IBM JDK 8 > {noformat} > [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.97 s <<< FAILURE! - in org.drools.compiler.integrationtests.MVELTest > [ERROR] testTypeCoercionLongDivByInt(org.drools.compiler.integrationtests.MVELTest) Time elapsed: 0.962 s <<< FAILURE! > java.lang.AssertionError: expected:<7.350000> but was:<7> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at org.drools.compiler.integrationtests.MVELTest.testTypeCoercionLongDivByInt(MVELTest.java:1150) > ... > [INFO] > [INFO] Results: > [INFO] > [ERROR] Failures: > [ERROR] MVELTest.testTypeCoercionLongDivByInt:1150 expected:<7.350000> but was:<7> > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 May 2020