October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1892) Add ability to KeyStoreCredentialStore to use Provider[] for passwords.

by Ilia Vassilev (Jira)

Ilia Vassilev created ELY-1892: ---------------------------------- Summary: Add ability to KeyStoreCredentialStore to use Provider[] for passwords. Key: ELY-1892 URL: https://issues.jboss.org/browse/ELY-1892 Project: WildFly Elytron Issue Type: Feature Request Components: Credential Store Affects Versions: 1.10.0.CR1 Reporter: Ilia Vassilev Assignee: Ilia Vassilev The KeyStoreCredentialStore implementation does not use the Provider[] passed in during initialisation for PasswordFactory interaction. However it does use it for the underlying KeyStore. Any changes here will need to consider backwards compatibility as existing users may be used to this difference. Elytron Tool: Add new option to Credential Store command to utilize the new feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1833) Add ability to KeyStoreCredentialStore to use Provider[] for passwords.

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/ELY-1833?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev updated ELY-1833: ------------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/1341 (was: https://github.com/wildfly-security/wildfly-elytron/pull/1331) > Add ability to KeyStoreCredentialStore to use Provider[] for passwords. > ----------------------------------------------------------------------- > > Key: ELY-1833 > URL: https://issues.jboss.org/browse/ELY-1833 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Credential Store > Affects Versions: 1.10.0.CR1 > Reporter: Darran Lofthouse > Assignee: Ilia Vassilev > Priority: Major > > The KeyStoreCredentialStore implementation does not use the Provider[] passed in during initialisation for PasswordFactory interaction. However it does use it for the underlying KeyStore. Any changes here will need to consider backwards compatibility as existing users may be used to this difference. > Elytron Tool: Add new option to Credential Store command to utilize the new feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3566) DMN:Detailed interactions for creating and managing DRDs

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3566?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3566: ------------------------------------------- [~tirelli] Yes, I understand the concern. * In my earlier mockups, I had also proposed Navigator tree actions for creating the DRD, and that did have more explicit controls, the little (+) button. I didn't include that in this mockup, cause I was waiting to learn the fate of the Navigator panel. But given it's staying put for the time being, I'll include the tree actions in the updated mockup as well. Maybe that will help. > DMN:Detailed interactions for creating and managing DRDs > -------------------------------------------------------- > > Key: DROOLS-3566 > URL: https://issues.jboss.org/browse/DROOLS-3566 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: contextual-menu.png > > > Canvas node actions related to grouping and assigning to DRDs. > * As a user I want to easily select and group nodes on the canvas so that I can add them to a DRD or to create a new DRD. > (TBD) As a user I want to be able to be able to use the Navigator tree to create DRD's and assign canvas nodes, so that I can easily modify my graph views. > Notes: > Navigator Tree actions TBD: > * Drag nodes to DRDs. > * Contextual menu for tree objects? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12676) memory leak, org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover$IdleRemoverRunner is keeping deployment in memory after undeployment

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12676?page=com.atlassian.jira.plugin... ] Scott Marlow reassigned WFLY-12676: ----------------------------------- Assignee: Scott Marlow (was: Stefano Maestri) > memory leak, org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover$IdleRemoverRunner is keeping deployment in memory after undeployment > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12676 > URL: https://issues.jboss.org/browse/WFLY-12676 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 18.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Blocker > Fix For: 19.0.0.Beta1 > > Attachments: 2lc.jar, java_pid12802.0001.zip, jcaleakmarlow.txt > > > As part of looking at [WFLY-12671], I found that org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover$IdleRemoverRunner is leaking the application classloader (after undeployment) via org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory originalTCCL being kept after undeployment. > See attached jcaleakmarlow.txt (also attached to [WFLY-12671]), which shows the leak. > I tried waiting a few minutes after undeployment and the leak was still there. I also tried an even simpler app (2lc.jar) and still there is a leak. I also attached the heapdump (java_pid12802.0001.zip) > To recreate: > * Deploy simple (no app code will be executed) 2lc.jar app. > * Undeploy by doing "rm 2lc.jar.deployed" in wildfly/standalone/deployments > * Look at memory with MAT or other memory leak tool. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12671) Memory Leak of PersistenceUnitMetadataImpl

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12671?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-12671: ------------------------------------- Thanks again for reporting this [~rschimpf]! I really appreciate that you raised this issue! I created [WFLY-12676] for the memory leak shown in (attachment) jcaleakmarlow.txt, that I see on WildFly 18.0.0.Final. If you do see the same leak, you get credit for reporting it (we can close WFLY-12676 as a duplicate of this issue). If not, your help in finding this leak, is still greatly appreciated! > Memory Leak of PersistenceUnitMetadataImpl > ------------------------------------------ > > Key: WFLY-12671 > URL: https://issues.jboss.org/browse/WFLY-12671 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 17.0.1.Final > Reporter: Robin Schimpf > Assignee: Scott Marlow > Priority: Major > Attachments: Trying_to_catch_memory_leak_with_more_trace_logging.patch, jcaleakmarlow.txt, memory leak after 4 deployments.PNG, memory leak after 5 deployments.PNG, memory leak with directory scanner undeploy and deploy.PNG, persistence-unit-not-stopped.txt, persistence-unit-stopped.txt > > > After updating from Wildfly 13 to Wildfly 17 we noticed a slowdown of our application after multiple deployments to the application server without restarting it between the deployments. Heapdumps are showing that after redeployment the number of {{PersistenceUnitMetadataImpl}} are growing (see screenshots). > We are deploying 2 ear files and 2 war files. Only one ear has a database connection configured. We are using the bundeled hibernate version of Wildfly 17. > The ear structure is like the following: > {noformat} > - app.ear > | > |- META-INF > | > |- lib > | | > | |- all dependencies > | > |- own jars and wars (e.g. jpa) > {noformat} > Since I failed to create a reproducing project for this behaviour I added some trace logging (Patch attached). The only difference I noticed was that sometimes the {{Stopping Persistence Unit}} logstatement is missing before the {{Stopped subdeployment}} logstatement. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3566) DMN:Detailed interactions for creating and managing DRDs

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3566?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-3566: --------------------------------------- Ok, I am not sure users will be aware of it, but we can deal with that later as part of the ticket michael mentioned. > DMN:Detailed interactions for creating and managing DRDs > -------------------------------------------------------- > > Key: DROOLS-3566 > URL: https://issues.jboss.org/browse/DROOLS-3566 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: contextual-menu.png > > > Canvas node actions related to grouping and assigning to DRDs. > * As a user I want to easily select and group nodes on the canvas so that I can add them to a DRD or to create a new DRD. > (TBD) As a user I want to be able to be able to use the Navigator tree to create DRD's and assign canvas nodes, so that I can easily modify my graph views. > Notes: > Navigator Tree actions TBD: > * Drag nodes to DRDs. > * Contextual menu for tree objects? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4625) Scenario Test: UX for background data error reporting

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4625?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4625: ------------------------------------------- ^^ and assuming background cells would get error highlighting treatment if applicable... > Scenario Test: UX for background data error reporting > ----------------------------------------------------- > > Key: DROOLS-4625 > URL: https://issues.jboss.org/browse/DROOLS-4625 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Jozef Marko > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screenshot from 2019-10-16 16-42-25.png, Screenshot from 2019-10-16 16-44-18.png, background-error.png, wrong-data.png > > > As a user I want to be informed about errors that occurred in the data I provided in the new *Background* tab. For more details about the *Backround* tab please see DROOLS-4162 and BAPL-1401. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12676) memory leak, org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover$IdleRemoverRunner is keeping deployment in memory after undeployment

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12676?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-12676: ------------------------------------- created [https://github.com/ironjacamar/ironjacamar/pull/692] + [https://issues.jboss.org/browse/JBJCA-1394] > memory leak, org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover$IdleRemoverRunner is keeping deployment in memory after undeployment > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12676 > URL: https://issues.jboss.org/browse/WFLY-12676 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 18.0.0.Final > Reporter: Scott Marlow > Assignee: Stefano Maestri > Priority: Blocker > Fix For: 19.0.0.Beta1 > > Attachments: 2lc.jar, java_pid12802.0001.zip, jcaleakmarlow.txt > > > As part of looking at [WFLY-12671], I found that org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover$IdleRemoverRunner is leaking the application classloader (after undeployment) via org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory originalTCCL being kept after undeployment. > See attached jcaleakmarlow.txt (also attached to [WFLY-12671]), which shows the leak. > I tried waiting a few minutes after undeployment and the leak was still there. I also tried an even simpler app (2lc.jar) and still there is a leak. I also attached the heapdump (java_pid12802.0001.zip) > To recreate: > * Deploy simple (no app code will be executed) 2lc.jar app. > * Undeploy by doing "rm 2lc.jar.deployed" in wildfly/standalone/deployments > * Look at memory with MAT or other memory leak tool. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4625) Scenario Test: UX for background data error reporting

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4625?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4625: ------------------------------------------- OK, so how about opening the Background tab in this case, and showing a dismissible inline alert. I've mocked that up (though the close button for the alert is scrolled out of view in this example.) But it would look like this: https://www.patternfly.org/v3/pattern-library/communication/inline-notifi... !wrong-data.png|thumbnail! Otherwise, same concept but using a [Toast notification|https://www.patternfly.org/v3/pattern-library/communication/...]. Although my concern with the toasts is that there are so many weird toasts in the workbench, people have probably stopped looking at them too closely. > Scenario Test: UX for background data error reporting > ----------------------------------------------------- > > Key: DROOLS-4625 > URL: https://issues.jboss.org/browse/DROOLS-4625 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Jozef Marko > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screenshot from 2019-10-16 16-42-25.png, Screenshot from 2019-10-16 16-44-18.png, background-error.png, wrong-data.png > > > As a user I want to be informed about errors that occurred in the data I provided in the new *Background* tab. For more details about the *Backround* tab please see DROOLS-4162 and BAPL-1401. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4625) Scenario Test: UX for background data error reporting

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4625?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4625: -------------------------------------- Attachment: wrong-data.png > Scenario Test: UX for background data error reporting > ----------------------------------------------------- > > Key: DROOLS-4625 > URL: https://issues.jboss.org/browse/DROOLS-4625 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Jozef Marko > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screenshot from 2019-10-16 16-42-25.png, Screenshot from 2019-10-16 16-44-18.png, background-error.png, wrong-data.png > > > As a user I want to be informed about errors that occurred in the data I provided in the new *Background* tab. For more details about the *Backround* tab please see DROOLS-4162 and BAPL-1401. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 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 October 2019