August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4599) Default AuthenticationContext is a static with undefined behaviour

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4599?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-4599: ------------------------------------- Fix Version/s: 10.0.0.Beta4 > Default AuthenticationContext is a static with undefined behaviour > ------------------------------------------------------------------ > > Key: WFCORE-4599 > URL: https://issues.jboss.org/browse/WFCORE-4599 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Priority: Major > Fix For: 10.0.0.Beta4 > > > The default AuthenticationContext global supplier initializes a static based on wildfly-config..xml found in the current class loader. > As this is initialised lazily the result of this will depend on which deployment is used to access this first. If there are multiple deployments other deployments can end up using the wrong configuration. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2362) Providing logical member name in JDBC_PING

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2362?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2362: -------------------------------- Glad to know it works! Cheers, > Providing logical member name in JDBC_PING > ------------------------------------------ > > Key: JGRP-2362 > URL: https://issues.jboss.org/browse/JGRP-2362 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 4.0.17, 4.0.18, 4.0.19, 4.1.0, 4.0.20 > Reporter: S Pokutniy > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1.3 > > > When using JDBC_PING and logical names instead of UUIDs and one of the cluster member crashes or get killed and this member is not coordinator then its database set still remains in the database as long as coordinator changes (independently from remove_old_coords_on_view_change /remove_all_data_on_view_change). If the the cluster is then restarted the old dataset makes connect() much slower (+30 seconds), as the members seem to be tryting to connect to it. Parameter remove_all_data_on_view_change seems to be the solution but it does not work as long as coordinator does not change, so practically the same as remove_old_coords_on_view_change. > The only solution seems to be to provide an appropriate delete statement in parameter initialize_sql, which would delete old entry, for example like this: delete from JGROUPSPING where ping_data like '%logical name%'. However, this is neither really quick nor the ideal solution, as ping_data's datatype is bytea or bit varying. > It would be great to have also logical name in JGROUPSPING, which is instead per default in insert(). This is also easy to implement as there is access to this information in PingData. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4403) Scenario Simulation: Export DMN/Rule runner logs

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4403?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-4403: ------------------------------------- Description: Export runner information for DMN/Rule-scesim (was: Export runner information for DMN-scesim) > Scenario Simulation: Export DMN/Rule runner logs > ------------------------------------------------ > > Key: DROOLS-4403 > URL: https://issues.jboss.org/browse/DROOLS-4403 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation, ScenarioSimulationTeam > > Export runner information for DMN/Rule-scesim -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4403) Scenario Simulation: Export DMN/Rule runner logs

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4403?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-4403: ------------------------------------- Summary: Scenario Simulation: Export DMN/Rule runner logs (was: Scenario Simulation: Export DMN runner logs) > Scenario Simulation: Export DMN/Rule runner logs > ------------------------------------------------ > > Key: DROOLS-4403 > URL: https://issues.jboss.org/browse/DROOLS-4403 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation, ScenarioSimulationTeam > > Export runner information for DMN-scesim -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4426) Remove version.org.kie property from droolsjbpm-build-bootstrap project

by Enrique Mingorance Cano (Jira)

Enrique Mingorance Cano created DROOLS-4426: ----------------------------------------------- Summary: Remove version.org.kie property from droolsjbpm-build-bootstrap project Key: DROOLS-4426 URL: https://issues.jboss.org/browse/DROOLS-4426 Project: Drools Issue Type: Bug Affects Versions: 7.24.0.Final Reporter: Enrique Mingorance Cano Assignee: Mario Fusco The property "version.org.kie" is already defined in the kie-parent project and it should removed from droolsjbpm-build-bootstrap project https://github.com/kiegroup/droolsjbpm-build-bootstrap/blob/bc4de568cac27... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2362) Providing logical member name in JDBC_PING

by S Pokutniy (Jira)

[ https://issues.jboss.org/browse/JGRP-2362?page=com.atlassian.jira.plugin.... ] S Pokutniy commented on JGRP-2362: ---------------------------------- My first tests are successful - many thanks for the quick resolution - it is really greatly appreciated. > Providing logical member name in JDBC_PING > ------------------------------------------ > > Key: JGRP-2362 > URL: https://issues.jboss.org/browse/JGRP-2362 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 4.0.17, 4.0.18, 4.0.19, 4.1.0, 4.0.20 > Reporter: S Pokutniy > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1.3 > > > When using JDBC_PING and logical names instead of UUIDs and one of the cluster member crashes or get killed and this member is not coordinator then its database set still remains in the database as long as coordinator changes (independently from remove_old_coords_on_view_change /remove_all_data_on_view_change). If the the cluster is then restarted the old dataset makes connect() much slower (+30 seconds), as the members seem to be tryting to connect to it. Parameter remove_all_data_on_view_change seems to be the solution but it does not work as long as coordinator does not change, so practically the same as remove_old_coords_on_view_change. > The only solution seems to be to provide an appropriate delete statement in parameter initialize_sql, which would delete old entry, for example like this: delete from JGROUPSPING where ping_data like '%logical name%'. However, this is neither really quick nor the ideal solution, as ping_data's datatype is bytea or bit varying. > It would be great to have also logical name in JGROUPSPING, which is instead per default in insert(). This is also easy to implement as there is access to this information in PingData. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-167) EAP Operator handling ConfigMap internally

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-167?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-167: ------------------------------------ This is opening whole new way how to configure EAP in openshift. And rise question how to apply EAP configuration runtime changes. So far applying runtime changes was not the question, because s2i configuration file was applied during building image. Is there plan operator will provide way how to apply runtime changes? E.g. rolling update in next phases? Or we are OK with declaring in documentation, that to apply runtime changes user have to restart pods himself. [~brian.stansberry] I know we have discussed before applying runtime changes is not a question in OpenShift environment . Are you aware we are going to support way how to change EAP configuration in runtime on openshift? Also [~luck3y] wdyt about proposed change? > EAP Operator handling ConfigMap internally > ------------------------------------------ > > Key: WFWIP-167 > URL: https://issues.jboss.org/browse/WFWIP-167 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > > If I understand description in [1] correctly. To specify custom standalone.xml I have to create ConfigMap with standalone.xml first and afterwards link operator to this ConfigMap. > Is it possible to handle creation of ConfigMap and storing standalone.xml for me? Ideally I just specify file URI where custom standalone.xml is located. This location have to be accessible from operator pod. In this way we can look at it as hiding internals (implementation details) from users. > Currently when user wants to change standalone.xml he does in ConfigMap, not operator. When changing standalone.xml through config map, I assume pod have to be restarted manually. Operator could do that for me. > However this can be triggered by storing newer version of standalone.xml under another key, eg `standalone.xml.v2` and changing `StandaloneConfigMapSpec.key` in operator. > What do you think? Have you considered this approach? > [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#sta... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4387) DMN editor: 7.6 Search - UX discovery/research

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4387?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4387: ------------------------------------------- [~tirelli] Oh okay, good to know, my misunderstanding. Thanks > DMN editor: 7.6 Search - UX discovery/research > ---------------------------------------------- > > Key: DROOLS-4387 > URL: https://issues.jboss.org/browse/DROOLS-4387 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > Follow-up to https://issues.jboss.org/browse/DROOLS-4142, to extend the Find feature to search across the entire DMN file/tabs within the editor. > This story is to gather use cases, requirements and acceptance criteria as defined at: https://www.yodiz.com/blog/user-stories-acceptance-definition-and-criteri... > Verification conditions: Documented use case and acceptance criteria for this feature, particularly as it relates to user experience and design. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4423) getObjectsDeep() leaks SubnetworkTuple instances

by cy x (Jira)

[ https://issues.jboss.org/browse/DROOLS-4423?page=com.atlassian.jira.plugi... ] cy x commented on DROOLS-4423: ------------------------------ Thank you all :) > getObjectsDeep() leaks SubnetworkTuple instances > ------------------------------------------------ > > Key: DROOLS-4423 > URL: https://issues.jboss.org/browse/DROOLS-4423 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Priority: Major > Attachments: bugReproducer with non-Engligsh characters removed.zip, bugReproducer.zip > > > https://stackoverflow.com/questions/57390971/optaplanner-i-tried-to-print... > Mario promised to take a look at fixing this if the user can provide a reproducer and they or QA isolate it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12371) Upgrade H2 from 1.4.193 to 1.4.199

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12371?page=com.atlassian.jira.plugin... ] Brian Stansberry edited comment on WFLY-12371 at 8/12/19 5:38 PM: ------------------------------------------------------------------ The upgrade causes testsuite failures of the form described at https://stackoverflow.com/questions/55349373/database-not-found-and-ifexi... For example https://ci.wildfly.org/viewLog.html?buildId=161535&tab=buildResultsDiv&bu... Not worth it. was (Author: brian.stansberry): The upgrade causes testsuite failures of the form described at https://stackoverflow.com/questions/55349373/database-not-found-and-ifexi... Not worth it. > Upgrade H2 from 1.4.193 to 1.4.199 > ---------------------------------- > > Key: WFLY-12371 > URL: https://issues.jboss.org/browse/WFLY-12371 > Project: WildFly > Issue Type: Component Upgrade > Components: JCA > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > https://github.com/h2database/h2database/compare/version-1.4.193...versio... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 August 2019