July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13144) Resource Adapter can't be deleted after restarting server

by Dmitrii Pogorelov (Jira)

[ https://issues.redhat.com/browse/WFLY-13144?page=com.atlassian.jira.plugi... ] Dmitrii Pogorelov commented on WFLY-13144: ------------------------------------------ [~shawkins] thx a lot! I tried the idea to remove the connection-definitions before removing the resource-adapter and it worked! The workaround for the workflow which I described in scope of the issue is the following (to remove the jcaDemo_VDB_ID_1 resource adapter after restarting WildFly server): {code:java} /subsystem=resource-adapters/resource-adapter=jcaDemo_VDB_ID_1/connection-definitions=jcaDemo_VDB_ID_1:remove{allow-resource-service-restart=true} /subsystem=resource-adapters/resource-adapter=jcaDemo_VDB_ID_1:remove{allow-resource-service-restart=true} {code} > Resource Adapter can't be deleted after restarting server > --------------------------------------------------------- > > Key: WFLY-13144 > URL: https://issues.redhat.com/browse/WFLY-13144 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 14.0.1.Final, 11.0.0.Final, 17.0.1.Final > Reporter: Dmitrii Pogorelov > Assignee: Ivo Studensky > Priority: Critical > Attachments: jca-demo-1.0.rar, jcademo-source-code.rar > > > The issue is related to the WFLY-6774 issue. I'm working with Teiid and should create/delete resource adapters many times, especially resource adapters based on the same archive. The WFLY-6774 fix works well before the restarting server allowing me to create/delete resource adapters without restarting the server. Once I restart the server and try to remove a resource adapter based on an archive I'll get the following error: > {code:noformat} > [standalone@localhost:9990 /] /subsystem=resource-adapters/resource-adapter=jcaDemo_VDB_ID_1:remove{allow-resource-service-restart=true} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies: > Service jboss.resourceadapters.ra.jcaDemo_VDB_ID_1 was depended upon by service jboss.deployment.unit.\"jca-demo-1.0.rar\".INSTALL", > "rolled-back" => true > } > {code} > After showing the error server will rollback the "remove" command deploying the jca-demo-1.0.rar archive again and re-creating the jcaDemo_VDB_ID_1 resource adapter. As a result I can't remove the resource adapter via cli commands, it can be removed only manually (removing the resource adapter in standalone.xml). The bug can be reproduced (at least versions which I checked) on WildFly 11.0.0.Final, WildFly 14.0.1.Final and WildFly 17.0.1.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13645) Provide a set of EAP XP QuickStarts that can run on OpenShift

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-13645?page=com.atlassian.jira.plugi... ] Eduardo Martins moved EAP7-1520 to WFLY-13645: ---------------------------------------------- Project: WildFly (was: JBoss EAP Planning for version 7 and above) Key: WFLY-13645 (was: EAP7-1520) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: Quickstarts (was: Quickstarts) EAP PT Pre-Checked (PC): (was: TODO) Target Release: (was: EAP-XP-2.0.0.GA) EAP PT Community Docs (CD): (was: TODO) EAP PT Product Docs (PD): (was: New) EAP PT Test Dev (TD): (was: TODO) EAP PT Docs Analysis (DA): (was: TODO) EAP PT Test Plan (TP): (was: TODO) EAP PT Analysis Document (AD): (was: TODO) > Provide a set of EAP XP QuickStarts that can run on OpenShift > -------------------------------------------------------------- > > Key: WFLY-13645 > URL: https://issues.redhat.com/browse/WFLY-13645 > Project: WildFly > Issue Type: Feature Request > Components: Quickstarts > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > The Quickstarts distributed in JBoss EAP XP should be made compatible with JBoss EAP XP Openshift images and templates. > Please note that JBoss EAP XP Quickstarts, to be considered Openshift compatible, goes beyond “it is deployed to Openshift without errors”, and “all functionality works when running on Openshift”, the documentation of such Quickstarts also need to include the *supported* Openshift usage instructions (specific asciidoc sections which QE tests), similar to the ones included with JBoss EAP CD Quickstarts. > Also similar to JBoss EAP CD releases, a live branch of JBoss EAP XP Quickstarts for Openshift should be prepared at the JBoss Developer source repository, which the JBoss EAP XP OpenShift Templates should point to, so users may easily discovery and create new projects with JBoss EAP XP Quickstarts. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5230) Managing a List of structures in Test Scenario editor produces an Exception

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5230?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5230: ------------------------------- Fix Version/s: (was: 7.41.0.Final) > Managing a List of structures in Test Scenario editor produces an Exception > --------------------------------------------------------------------------- > > Key: DROOLS-5230 > URL: https://issues.redhat.com/browse/DROOLS-5230 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.34.0.Final > Reporter: Tracy Hires > Assignee: Yeser Amer > Priority: Critical > Attachments: Error screen shot.png, test_scenario_list_exception.zip > > > When trying to delete an item from a list of structures with nested structures in the scenario editor, an exception is thrown with a message that is not helpful to the end user. > Log entry is: > ``` > ^[[0m^[[31m17:16:51,564 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-415) Error from user: xxxxx Error ID: -881202734 Location: LibraryPerspective|$ProjectScreen[!Worg.kie.dmn.decision.navigator,EDiagramEditorPropertiesScreen,Eorg.drools.scenariosimulation.TestTools?scesimeditorid=1,!Eorg.drools.scenariosimulation.TestTools?scesimeditorid=2,Eorg.docks.PlaceHolder?name=testRunnerReportingPanel,Worg.kie.guvnor.explorer,],DMNDiagramEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/main/resources/Math%2520Functions.dmn&file_name=Math%20Functions.dmn&has_version_support=true,DMNDiagramEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/main/resources/Divide.dmn&file_name=Divide.dmn&has_version_support=true,org.kie.workbench.common.screens.messageconsole.MessageConsole,,AddAssetsScreen,ScenarioSimulationEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/test/resources/Test%2520Math%2520Functions.scesim&file_name=Test%20Math%20Functions.scesim&has_version_support=true Exception: Uncaught exception: Exception caught: (TypeError) : Cannot read property 'Tc' of undefined Caused by: (TypeError) : Cannot read property 'Tc' of undefined > ``` > From UI I could see: `Uncaught exception: Exception caught: (TypeError) : Cannot read property 'Tc' of undefined Caused by: (TypeError) : Cannot read property 'Tc' of undefined` > (Screenshot is attached) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5035) Add a new legacy-security artefact / module

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-5035: ---------------------------------------- Summary: Add a new legacy-security artefact / module Key: WFCORE-5035 URL: https://issues.redhat.com/browse/WFCORE-5035 Project: WildFly Core Issue Type: Task Components: Build System, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 13.0.0.Beta2 Where components in WildFly Core depend on PicketBox we should make sure this is via a module which they can optional depend upon so avoid components in WildFly Core having hard dependencies on PicketBox APIs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-2007) Bring SecurityIdentity PolicyContextHandler inline with WildFly Core implementation.

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-2007?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated ELY-2007: ---------------------------------- Description: There is an implementation in WildFly Core which uses SecurityDomain.getCurrent() - move this to the Elytron implementation. (was: There is an implementation in WildFly Core but really the implementation is not specific to the integration in the application server so it should be moved into the WildFly Elytron project.) > Bring SecurityIdentity PolicyContextHandler inline with WildFly Core implementation. > ------------------------------------------------------------------------------------ > > Key: ELY-2007 > URL: https://issues.redhat.com/browse/ELY-2007 > Project: WildFly Elytron > Issue Type: Enhancement > Components: EE > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.13.0.CR2 > > > There is an implementation in WildFly Core which uses SecurityDomain.getCurrent() - move this to the Elytron implementation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-2007) Bring SecurityIdentity PolicyContextHandler inline with WildFly Core implementation.

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-2007?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated ELY-2007: ---------------------------------- Summary: Bring SecurityIdentity PolicyContextHandler inline with WildFly Core implementation. (was: Add SecurityIdentity PolicyContextHandler) > Bring SecurityIdentity PolicyContextHandler inline with WildFly Core implementation. > ------------------------------------------------------------------------------------ > > Key: ELY-2007 > URL: https://issues.redhat.com/browse/ELY-2007 > Project: WildFly Elytron > Issue Type: Enhancement > Components: EE > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.13.0.CR2 > > > There is an implementation in WildFly Core but really the implementation is not specific to the integration in the application server so it should be moved into the WildFly Elytron project. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5034) Upgrade log4j to 2.13.3

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-5034?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-5034: -------------------------------- Issue Type: Component Upgrade (was: Feature Request) > Upgrade log4j to 2.13.3 > ----------------------- > > Key: WFCORE-5034 > URL: https://issues.redhat.com/browse/WFCORE-5034 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Test Suite > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > > The embedded test suite uses Log4J 2.11.0 when its tests are run. > The version should be upgrade to 2.13.3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-2008) Move JACC tests into JACC module

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-2008: ------------------------------------- Summary: Move JACC tests into JACC module Key: ELY-2008 URL: https://issues.redhat.com/browse/ELY-2008 Project: WildFly Elytron Issue Type: Enhancement Components: EE, Testsuite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.13.0.CR2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13639) Avoid duplicate expiration scheduling on member leave for non-tx invalidation cache

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13639?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13639: -------------------------------- Description: Following WFLY-13627, a non-tx invalidation cache will schedule session/SFSB expiration on the local member. When that member leaves, the expiration will be reschedule on the primary owner of segment 0 (in a non-tx cache, all entries map to segment 0). However, since that member cannot distinguish which sessions/SFSBs were owned by the leaving member, it must schedule all sessions/SFSBs. (was: Following WFLY-13627, a non-tx invalidation cache will schedule session/SFSB expiration on the local member. When that member leaves, the expiration will be reschedule on the primary owner of segment 0 (in a non-tx cache, all entries map to segment 0). However, since that member cannot distinguish which sessions/SFSBs were owned by the leaving member, it must schedule all sessions/SFSBs. By storing the address of the member that handled a given request along with a web session/SFSBs metadata, we can discriminate which entries require expiration rescheduling on topology change for non-tx invalidation caches.) > Avoid duplicate expiration scheduling on member leave for non-tx invalidation cache > ----------------------------------------------------------------------------------- > > Key: WFLY-13639 > URL: https://issues.redhat.com/browse/WFLY-13639 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Following WFLY-13627, a non-tx invalidation cache will schedule session/SFSB expiration on the local member. When that member leaves, the expiration will be reschedule on the primary owner of segment 0 (in a non-tx cache, all entries map to segment 0). However, since that member cannot distinguish which sessions/SFSBs were owned by the leaving member, it must schedule all sessions/SFSBs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5034) Upgrade log4j to 2.13.3

by Jeff Mesnil (Jira)

Jeff Mesnil created WFCORE-5034: ----------------------------------- Summary: Upgrade log4j to 2.13.3 Key: WFCORE-5034 URL: https://issues.redhat.com/browse/WFCORE-5034 Project: WildFly Core Issue Type: Feature Request Components: Test Suite Reporter: Jeff Mesnil Assignee: Jeff Mesnil The embedded test suite uses Log4J 2.11.0 when its tests are run. The version should be upgrade to 2.13.3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2020