July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13651) Make AbstractEJBComponentResourceDefinition.METHODS an ObjectMapAttributeDefinition (rather than ObjectListAD)

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFLY-13651?page=com.atlassian.jira.plugi... ] Kabir Khan commented on WFLY-13651: ----------------------------------- This should pass the testsuite without a core upgrade, however if we want to fix EAPSUP-191 we will also need WFCORE-5037. [~cfang] If you think we should add some tests for this, please take over my WildFly PR and add those? > Make AbstractEJBComponentResourceDefinition.METHODS an ObjectMapAttributeDefinition (rather than ObjectListAD) > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-13651 > URL: https://issues.redhat.com/browse/WFLY-13651 > Project: WildFly > Issue Type: Bug > Components: EJB, JMX > Reporter: Kabir Khan > Assignee: Cheng Fang > Priority: Major > > See EAPSUP-191 for details. > This does not need a model version bump since the r-r-d output is the same for ObjectMap- and ObjectListAttributeDefinition. We need to use ObjectMapAttributeDefinition as a 'signal' to the improvements in WFCORE-5037. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13641) WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml

by Jens Viebig (Jira)

[ https://issues.redhat.com/browse/WFLY-13641?page=com.atlassian.jira.plugi... ] Jens Viebig edited comment on WFLY-13641 at 7/8/20 5:38 AM: ------------------------------------------------------------ Here is some documentation about cross-module CDI and jboss-deployment-structure [https://docs.wildfly.org/17/Developer_Guide.html#CDI_Reference] >From my understanding cross-module CDI should only ever be activated if you specify meta-inf="import" on a dependency. But this is not the case for our deployments was (Author: jviebig): Here is some documentation about cross-module CDI and jboss-deploymet-structure [https://docs.wildfly.org/17/Developer_Guide.html#CDI_Reference] >From my understanding cross-module CDI should only ever be activated if you specify meta-inf="import" on a dependency. But this is not the case for our deployments > WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-13641 > URL: https://issues.redhat.com/browse/WFLY-13641 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 20.0.0.Final > Reporter: Jens Viebig > Assignee: Matěj Novotný > Priority: Major > > When referencing a jar with CDI scan mode "annotaded" inside an ear from an external war via jboss-deployment-structure.xml a warning will be printed for every class: > WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml > Seems VFS cannot get hold of the classes. > The warning is logged in ExternalBeanArchiveProcessor which catches an EOFException from the inputstream loading the class. (Line 284). Seems the input stream is not able to load a single byte from the class -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13177) ManagedExecutorService: Wrong activeRequestCount at RequestController on RejectedExecutionException

by Ivo Studensky (Jira)

[ https://issues.redhat.com/browse/WFLY-13177?page=com.atlassian.jira.plugi... ] Ivo Studensky reassigned WFLY-13177: ------------------------------------ Assignee: Ivo Studensky (was: Eduardo Martins) > ManagedExecutorService: Wrong activeRequestCount at RequestController on RejectedExecutionException > --------------------------------------------------------------------------------------------------- > > Key: WFLY-13177 > URL: https://issues.redhat.com/browse/WFLY-13177 > Project: WildFly > Issue Type: Bug > Components: Concurrency Utilities > Affects Versions: 13.0.0.Final, 16.0.0.Final > Reporter: Guido Jäkel > Assignee: Ivo Studensky > Priority: Critical > Fix For: 21.0.0.Beta1 > > > On WF-13 and WF-16 we observe a serious bug of the RequestCount of the RequestController while using ManagedExecutorService.submit() or ...execute() in the edge case of a full queue. In this case, the caller gets a RejectedExecutionException, but in the RequestController, the number of active requests is erroneously incremented. > This will lead to a false and monotonously increasing number of active requests. And in case of a limitation configured by the maxRequestCount feature, which is best practice for production environments, over the time this will lead to deadlock of the RequestController and herewith the complete activity of the Wildfly at all. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1155) UI Automations Labels for Applications

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1155?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1155. ----------------------------------- Resolution: Done > UI Automations Labels for Applications > -------------------------------------- > > Key: SWSQE-1155 > URL: https://issues.redhat.com/browse/SWSQE-1155 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > It is commented and TODO: Service name label should be taken from OC. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1187) Workloads list test - Add back labels comparison

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1187?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1187. ----------------------------------- Resolution: Done > Workloads list test - Add back labels comparison > ------------------------------------------------ > > Key: SWSQE-1187 > URL: https://issues.redhat.com/browse/SWSQE-1187 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Label comparison between OC and UI. > In Workloads lists test. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5485) Move test cases from drools-compiler to drools-test-coverage

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5485?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5485: -------------------------------------- Description: Move test cases from drools-compiler to drools-test-coverage/test-compiler-integration so that we can increase the test coverage for executable-model. At the moment, I'm not yet sure how many of the test cases can be moved. Basically DRL based test only. Luca noted: > there are some tests in -compiler that are not supported in the model compiler (I'm thinking about all the ASM/type generation related). That should be left in -compiler and hopefully moved outside like the traits If we find test failures by executable-model, we would spawn new JIRAs to deal with them one-by-one. was: Move test cases from drools-compiler to drools-model-compiler so that we can increase the test coverage for executable-model. At the moment, I'm not yet sure how many of the test cases can be moved. Basically DRL based test only. Luca noted: > there are some tests in -compiler that are not supported in the model compiler (I'm thinking about all the ASM/type generation related). That should be left in -compiler and hopefully moved outside like the traits If we find test failures by executable-model, we would spawn new JIRAs to deal with them one-by-one. > Move test cases from drools-compiler to drools-test-coverage > ------------------------------------------------------------ > > Key: DROOLS-5485 > URL: https://issues.redhat.com/browse/DROOLS-5485 > Project: Drools > Issue Type: Task > Components: core engine, executable model > Affects Versions: 7.39.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Move test cases from drools-compiler to drools-test-coverage/test-compiler-integration so that we can increase the test coverage for executable-model. > At the moment, I'm not yet sure how many of the test cases can be moved. Basically DRL based test only. > Luca noted: > > there are some tests in -compiler that are not supported in the model compiler (I'm thinking about all the ASM/type generation related). That should be left in -compiler and hopefully moved outside like the traits > If we find test failures by executable-model, we would spawn new JIRAs to deal with them one-by-one. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5485) Move test cases from drools-compiler to drools-test-coverage

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5485?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5485: -------------------------------------- Summary: Move test cases from drools-compiler to drools-test-coverage (was: Move test cases from drools-compiler to drools-model-compiler) > Move test cases from drools-compiler to drools-test-coverage > ------------------------------------------------------------ > > Key: DROOLS-5485 > URL: https://issues.redhat.com/browse/DROOLS-5485 > Project: Drools > Issue Type: Task > Components: core engine, executable model > Affects Versions: 7.39.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Move test cases from drools-compiler to drools-model-compiler so that we can increase the test coverage for executable-model. > At the moment, I'm not yet sure how many of the test cases can be moved. Basically DRL based test only. > Luca noted: > > there are some tests in -compiler that are not supported in the model compiler (I'm thinking about all the ASM/type generation related). That should be left in -compiler and hopefully moved outside like the traits > If we find test failures by executable-model, we would spawn new JIRAs to deal with them one-by-one. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13654) Upgrade wildfly-http-client to 1.1.2.Final

by Tomasz Adamski (Jira)

[ https://issues.redhat.com/browse/WFLY-13654?page=com.atlassian.jira.plugi... ] Tomasz Adamski closed WFLY-13654. --------------------------------- Resolution: Duplicate Issue > Upgrade wildfly-http-client to 1.1.2.Final > ------------------------------------------ > > Key: WFLY-13654 > URL: https://issues.redhat.com/browse/WFLY-13654 > Project: WildFly > Issue Type: Component Upgrade > Components: Web (Undertow) > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Major > > [https://github.com/wildfly/wildfly-http-client/compare/1.1.1.Final...1.1....] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13654) Upgrade wildfly-http-client to 1.1.2.Final

by Tomasz Adamski (Jira)

[ https://issues.redhat.com/browse/WFLY-13654?page=com.atlassian.jira.plugi... ] Tomasz Adamski updated WFLY-13654: ---------------------------------- Description: [https://github.com/wildfly/wildfly-http-client/compare/1.1.1.Final...1.1....] > Upgrade wildfly-http-client to 1.1.2.Final > ------------------------------------------ > > Key: WFLY-13654 > URL: https://issues.redhat.com/browse/WFLY-13654 > Project: WildFly > Issue Type: Component Upgrade > Components: Web (Undertow) > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Major > > [https://github.com/wildfly/wildfly-http-client/compare/1.1.1.Final...1.1....] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13654) Upgrade wildfly-http-client to 1.1.2.Final

by Tomasz Adamski (Jira)

Tomasz Adamski created WFLY-13654: ------------------------------------- Summary: Upgrade wildfly-http-client to 1.1.2.Final Key: WFLY-13654 URL: https://issues.redhat.com/browse/WFLY-13654 Project: WildFly Issue Type: Component Upgrade Components: Web (Undertow) Reporter: Tomasz Adamski Assignee: Tomasz Adamski -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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 July 2020