March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4362) Make the certificate authority used by a certificate-authority-account configurable

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4362?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-4362: ------------------------------------- Labels: (was: EAP-CD17) > Make the certificate authority used by a certificate-authority-account configurable > ----------------------------------------------------------------------------------- > > Key: WFCORE-4362 > URL: https://issues.jboss.org/browse/WFCORE-4362 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Priority: Major > > Currently, Let's Encrypt (https://acme-v02.api.letsencrypt.org/directory) is the only certificate authority that can be used by a {{certificate-authority-account}}. In the future, if/when other certificate authorities implement the server side of the ACME protocol, this will need to be configurable. In addition, making this configurable would also allow local Let's Encrypt server instances to be used for testing purposes. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4361) Enhanced mapping of X509Certificate to the underlying identity

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4361: ---------------------------------------- Summary: Enhanced mapping of X509Certificate to the underlying identity Key: WFCORE-4361 URL: https://issues.jboss.org/browse/WFCORE-4361 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Darran Lofthouse Fix For: 9.0.0.Beta1 Presently we support decoding the distinguished name however there are requests to use alternative such as the subject alternative name. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-627) Move Public Kiali (KProd) to New Location

by Matt Mahoney (Jira)

Matt Mahoney created SWSQE-627: ---------------------------------- Summary: Move Public Kiali (KProd) to New Location Key: SWSQE-627 URL: https://issues.jboss.org/browse/SWSQE-627 Project: Kiali QE Issue Type: Task Reporter: Matt Mahoney Assignee: Matt Mahoney Central CI is being decommissioned (date is TBD according to login page. This task is to migrate KProd to a new Openshift host. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

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

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3731: ------------------------------------- [~tirelli] [~manstis] I created this jira for the overlays. My understanding is that you're looking for something similar to the designs I created for Process Instance diagrams (attached) - show some indicator on a node plus a popover when hovered over? [~zhutaojiajia] Adding you to this thread, Edson suggested that we sync-up on this because you're working on a similar thing for Scenario. I linked all of the related jiras to this one. > 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: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam > 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)

6 years, 9 months

1
0
0 / 0

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

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3731: -------------------------------- Attachment: download (1).png download.png > 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: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam > 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)

6 years, 9 months

1
0
0 / 0

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

by Liz Clayton (Jira)

Liz Clayton created DROOLS-3731: ----------------------------------- Summary: 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: Liz Clayton Assignee: Liz Clayton 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)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4360) Support encrypted expression resolution using a CredentialStore

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4360: ---------------------------------------- Summary: Support encrypted expression resolution using a CredentialStore Key: WFCORE-4360 URL: https://issues.jboss.org/browse/WFCORE-4360 Project: WildFly Core Issue Type: Feature Request Components: Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 9.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11811) Default transaction timeout coud be wrongly configured because of the TM initiation race condition

by Ondra Chaloupka (Jira)

Ondra Chaloupka created WFLY-11811: -------------------------------------- Summary: Default transaction timeout coud be wrongly configured because of the TM initiation race condition Key: WFLY-11811 URL: https://issues.jboss.org/browse/WFLY-11811 Project: WildFly Issue Type: Bug Components: Transactions Affects Versions: 16.0.0.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka Transaction default timeout could be wrongly set up because of race condition in configuration of the {{CoordinatorEnvironmentBean}} and the {{TxControl}} class which is used on transaction begin and loads data from the coordinator bean to static variable. The default transaction timeout defined by Narayana is 60 seconds. It's coded in source at https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes... The {{CoordinatorEnvironmentBean}} is instantiated with the default value or with value taken from system property or xml descriptor (https://jbossts.blogspot.com/2018/01/narayana-periodic-recovery-of-xa.htm...). When new transaction is started it does not use directly the {{CoordinatorEnvironmentBean#getDefaultTimeout()}} but the {{TxControl#getDefaultTimeout()}} (https://github.com/jbosstm/narayana/blob/5.9.3.Final/ArjunaCore/arjuna/cl...). >From the [~stephen.fikes] testing with Byteman[1] when there is used the environment property {{-Dcom.arjuna.ats.arjuna.coordinator.defaultTimeout=301}} (should not be used for WFLY) and WFLY model configuration {{<coordinator-environment default-timeout="302"/>}} we can see the {{CoordinatorEnvironmentBean.setDefaultTimeout}} is called twice. First time it's time of the bean initialization and the value of 301 is taken ({{BeanPopulator}} instantiates the bean and reset the default value of {{60}} to {{301}}. Next the ArjunaTransactionManagerService is started and set the value to 302 as model defines https://github.com/wildfly/wildfly/blob/16.0.0.Final/transactions/src/mai.... Unfortunately, there is no changes for the {{TxControl}} class which is used during transaction startup. If the {{TxControl}} would be initialized before the {{ArjunaTransactionService}} is started then the value defined in the WFLY model would not be considered until a change in the CLI ({{/subsystem=transactions:write-attribute(name=default-timeout, value=100)}}) is done. The cli command causes the {{TxControl}} is reset - https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... We should ensure the {{TxControl._defaultTimeout}} value is configured during {{ArjunaTransactionManagerService}} start up as well. [1] {code} INFO [stdout] (MSC service thread 1-2) [BMAN] CoordinatorEnvironmentBean.setDefaultTimeout(301) com.arjuna.ats.arjuna.common.CoordinatorEnvironmentBean.setDefaultTimeout(CoordinatorEnvironmentBean.java:-1) sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:498) com.arjuna.common.internal.util.propertyservice.BeanPopulator.handleSimpleProperty(BeanPopulator.java:312) com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:172) com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:87) com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:53) com.arjuna.ats.arjuna.common.arjPropertyManager.getCoordinatorEnvironmentBean(arjPropertyManager.java:51) com.arjuna.ats.arjuna.coordinator.BasicAction.<clinit>(BasicAction.java:3754) com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.<clinit>(CommitMarkableResourceRecordRecoveryModule.java:79) java.lang.Class.forName0(Class.java:-2) java.lang.Class.forName(Class.java:264) com.arjuna.common.internal.util.ClassloadingUtility.loadClass(ClassloadingUtility.java:57) com.arjuna.common.internal.util.ClassloadingUtility.loadClass(ClassloadingUtility.java:85) com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:117) com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:192) com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:465) com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:883) com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.<init>(PeriodicRecovery.java:121) com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.<init>(RecoveryManagerImple.java:107) com.arjuna.ats.arjuna.recovery.RecoveryManager.<init>(RecoveryManager.java:477) com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:132) com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:112) com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:54) org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:126) org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748) INFO [stdout] (MSC service thread 1-2) [BMAN] CoordinatorEnvironmentBean.setDefaultTimeout(302) com.arjuna.ats.arjuna.common.CoordinatorEnvironmentBean.setDefaultTimeout(CoordinatorEnvironmentBean.java:-1) org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:88) org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748) {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11565) WildFly Server Adds Transfer Encoding Chunk Header to the HttpResponse with status code 204

by Soumya Khedagi (Jira)

[ https://issues.jboss.org/browse/WFLY-11565?page=com.atlassian.jira.plugin... ] Soumya Khedagi commented on WFLY-11565: --------------------------------------- Hi [~baranowb], gentle reminder. Please let me know if you need more info from us. > WildFly Server Adds Transfer Encoding Chunk Header to the HttpResponse with status code 204 > ------------------------------------------------------------------------------------------- > > Key: WFLY-11565 > URL: https://issues.jboss.org/browse/WFLY-11565 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.0.Final > Reporter: Deepak Sahu > Assignee: Bartosz Baranowski > Priority: Major > Attachments: API.war > > > I am using WildFly Server 9.0.0 Final, Javax ws, Jersey for developing Rest APIs. For all the responses whose httpStatus code is 204, the wildfly server adds Transfer encoding Chunked in the response header, which is not correct as per the Rest Standards. Because of this behavior some of the RestAPI clients hang, as they keep waiting for the response (which is not at all there). > To verify the issue, I tried the same with Springboot instead of deploying the war in WildFly and the Response Header was not added with Transfer Encoding Chuncked. > Let me know if some other information is required to fix this issue, if this is already fixed is there any patch for this issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-241) Expose the current LogContextSelector from the LogContext

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-241?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-241: --------------------------------- Fix Version/s: 2.1.8.Final (was: 2.1.7.Final) > Expose the current LogContextSelector from the LogContext > --------------------------------------------------------- > > Key: LOGMGR-241 > URL: https://issues.jboss.org/browse/LOGMGR-241 > Project: JBoss Log Manager > Issue Type: Enhancement > Components: core > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 2.1.8.Final, 3.0.0.Final, 2.2.0.Final > > > Currently you can set a {{LogContextSelector}} on a {{LogContext}} however there is no way to query the currently set selector. This could be useful in cases where you need to wrap a current selector in a new selector. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2019