May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12046) Some clustering test cases do not close JNDI InitialContext between tests

by Ilia Vassilev (Jira)

Ilia Vassilev created WFLY-12046: ------------------------------------ Summary: Some clustering test cases do not close JNDI InitialContext between tests Key: WFLY-12046 URL: https://issues.jboss.org/browse/WFLY-12046 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 17.0.0.Beta1 Reporter: Ilia Vassilev Assignee: Richard Achmatowicz Fix For: 17.0.0.Beta1 The test case RemoteStatelessFailoverTestCase makes use of the helper class EJBRemoteDirectory to lookup JNDI names for beans in test cases. The EJB client then uses the resulting proxies to make invocations on the beans. This helper class is defined statically and initialized before any of the test cases run. Consequenty, the InitialContext created by the helper class is used across multiple test cases. The effect of this is that all of the proxies used in the test case are created from the same InitialContext. Consequently, they share a RemoteEJBDiscoveryProvider instance which is a class used to maintain information about server and module deployments which the EJB client references during invocation to find a suitable target for the invocation. This means that any server startup or shutdown activities are passed from one test case to another. This is not wanted as crash failures or shutdowns in one test will contaminate the next test, and this is exactly what is happening in a particular failure of this test. If your test class only involves one test, then static usage will work, but probably not recommended. UPDATE: This problem is present in a few other test cases, so I have updated them. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3971) DRL compiler Quarkus extension

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-3971: -------------------------------------- Summary: DRL compiler Quarkus extension Key: DROOLS-3971 URL: https://issues.jboss.org/browse/DROOLS-3971 Project: Drools Issue Type: Task Reporter: Edoardo Vacchi Assignee: Edoardo Vacchi this issue depends on JBPM-8458 being merged -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3731: -------------------------------------- Story Points: 3 (was: 5) > DMN UX - More info overlaid on models. > -------------------------------------- > > Key: DROOLS-3731 > URL: https://issues.jboss.org/browse/DROOLS-3731 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: download (1).png, download.png > > > As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression. > Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12045) Some clustering test cases do not close JNDI InitialContext between tests

by Richard Achmatowicz (Jira)

Richard Achmatowicz created WFLY-12045: ------------------------------------------ Summary: Some clustering test cases do not close JNDI InitialContext between tests Key: WFLY-12045 URL: https://issues.jboss.org/browse/WFLY-12045 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 17.0.0.Beta1 Reporter: Richard Achmatowicz Assignee: Richard Achmatowicz Fix For: 17.0.0.Beta1 The test case RemoteStatelessFailoverTestCase makes use of the helper class EJBRemoteDirectory to lookup JNDI names for beans in test cases. The EJB client then uses the resulting proxies to make invocations on the beans. This helper class is defined statically and initialized before any of the test cases run. Consequenty, the InitialContext created by the helper class is used across multiple test cases. The effect of this is that all of the proxies used in the test case are created from the same InitialContext. Consequently, they share a RemoteEJBDiscoveryProvider instance which is a class used to maintain information about server and module deployments which the EJB client references during invocation to find a suitable target for the invocation. This means that any server startup or shutdown activities are passed from one test case to another. This is not wanted as crash failures or shutdowns in one test will contaminate the next test, and this is exactly what is happening in a particular failure of this test. If your test class only involves one test, then static usage will work, but probably not recommended. UPDATE: This problem is present in a few other test cases, so I have updated them. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3731: ------------------------------------------- Presentation suggestion documented at: https://issues.jboss.org/browse/DROOLS-3742 "For DMN Scenario we should implement a mechanism to open automatically a decision in the DMN Editor and highlight the reason why a decision has been taked (for instance the row of the decision table). UX proposed to open it in a popup ( https://redhat.invisionapp.com/share/MHQTRRJYATR#/screens/349225348 ) but I don't think it is really possible. I think it could be enough to have a way to call the DMN Editor and automatically open a specific decision." * Start with showing an error on the graph node. > DMN UX - More info overlaid on models. > -------------------------------------- > > Key: DROOLS-3731 > URL: https://issues.jboss.org/browse/DROOLS-3731 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: download (1).png, download.png > > > As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression. > Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3953) DMN UX - error highlight in boxed expression.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3953: -------------------------------------- Sprint: (was: 2019 Week 17-19) > DMN UX - error highlight in boxed expression. > --------------------------------------------- > > Key: DROOLS-3953 > URL: https://issues.jboss.org/browse/DROOLS-3953 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3731: -------------------------------------- Sprint: 2019 Week 11-13, 2019 Week 17-19 (was: 2019 Week 11-13) > DMN UX - More info overlaid on models. > -------------------------------------- > > Key: DROOLS-3731 > URL: https://issues.jboss.org/browse/DROOLS-3731 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: download (1).png, download.png > > > As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression. > Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3953) DMN UX - error highlight in boxed expression.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3953: ------------------------------------------- suggestion documented at: https://issues.jboss.org/browse/DROOLS-3742 * "For DMN Scenario we should implement a mechanism to open automatically a decision in the DMN Editor and highlight the reason why a decision has been taked (for instance the row of the decision table). UX proposed to open it in a popup ( https://redhat.invisionapp.com/share/MHQTRRJYATR#/screens/349225348 ) but I don't think it is really possible. I think it could be enough to have a way to call the DMN Editor and automatically open a specific decision." > DMN UX - error highlight in boxed expression. > --------------------------------------------- > > Key: DROOLS-3953 > URL: https://issues.jboss.org/browse/DROOLS-3953 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12019) Cannot remove a undertow server resource at one time

by Bartosz Spyrko (Jira)

[ https://issues.jboss.org/browse/WFLY-12019?page=com.atlassian.jira.plugin... ] Bartosz Spyrko commented on WFLY-12019: --------------------------------------- [~pferraro] I'm running into a problem with SSO manager installer service. When I remove the sso setting from host config using _allow-resource-service-restart=true_ and try to add it again without reload I'm get a failure: {noformat} [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/host=test-host/setting=single-sign-on:add {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/host=test-host/setting=single-sign-on:remove{allow-resource-service-restart=true} {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/host=test-host/setting=single-sign-on:add { "outcome" => "failed", "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service. DuplicateServiceException: Service jboss.undertow.server.default-server.test-host.single-si gn-on.manager.installer is already registered", "rolled-back" => true } {noformat} It looks like the installer service is created every time _DistributableSingleSignOnManagerServiceConfigurator_ is build, but never removed. Would it be OK to remove the service in _HostSingleSignOnServiceHandler_ together with _jboss.undertow.server.default-server.test-host.single-sign-on.manager_ service? Or is there a better way to ensure it's removed? > Cannot remove a undertow server resource at one time > ---------------------------------------------------- > > Key: WFLY-12019 > URL: https://issues.jboss.org/browse/WFLY-12019 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 16.0.0.Final > Reporter: Bartosz Spyrko > Assignee: Bartosz Spyrko > Priority: Major > > Cannot remove a server attribute. > {noformat} > [standalone@localhost:9990 /] /subsystem=undertow/server=default-server:remove() > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies: > Service jboss.undertow.server.default-server.default-host was depended upon by service jboss.undertow.server.default-server.default-host.filter-ref.x-powered-by-header, service jboss.undertow.server.default-server.default-host.location. > /, service jboss.undertow.server.default-server.default-host.filter-ref.server-header", > "rolled-back" => true, > "response-headers" => undefined > } > {noformat} > However, it can be removed executing same command again. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12035) Upgrade jberet-core from 1.3.3.Final to 1.3.4.Final

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-12035?page=com.atlassian.jira.plugin... ] Cheng Fang updated WFLY-12035: ------------------------------ Description: Need to upgrade jberet-core from the current version 1.3.3.Final to 1.3.4.Final, to include the fix that ensures https (instead of http) is used in maven repository links. https://github.com/jberet/jsr352/tree/1.3.x Delta: https://github.com/jberet/jsr352/compare/1.3.3.Final...1.3.4.Final The real changes that affect jberet-core are: * upgrade jboss-parent to 34 * upgrade jboss-logging to 3.4.0 * upgrade jboss-batch-api_1.0_spec to 1.0.2 (which was built with secure https maven repository links) * change to use https for maven repository links in build process was: Need to upgrade jberet-core from the current version 1.3.3.Final to 1.3.4.Final, to include the fix that ensures https (instead of http) is used in maven repository links. https://github.com/jberet/jsr352/tree/1.3.x > Upgrade jberet-core from 1.3.3.Final to 1.3.4.Final > --------------------------------------------------- > > Key: WFLY-12035 > URL: https://issues.jboss.org/browse/WFLY-12035 > Project: WildFly > Issue Type: Component Upgrade > Components: Batch > Affects Versions: 16.0.0.Final > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > Fix For: 17.0.0.Beta1 > > > Need to upgrade jberet-core from the current version 1.3.3.Final to 1.3.4.Final, to include the fix that ensures https (instead of http) is used in maven repository links. > https://github.com/jberet/jsr352/tree/1.3.x > Delta: https://github.com/jberet/jsr352/compare/1.3.3.Final...1.3.4.Final > The real changes that affect jberet-core are: > * upgrade jboss-parent to 34 > * upgrade jboss-logging to 3.4.0 > * upgrade jboss-batch-api_1.0_spec to 1.0.2 (which was built with secure https maven repository links) > * change to use https for maven repository links in build process -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 2019