January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12881) Cannot customize split behavior and merge policy for Infinispan partition handling

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12881?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12881: -------------------------------- Summary: Cannot customize split behavior and merge policy for Infinispan partition handling (was: Cannot customize split detection and merge policy for Infinispan partition handling) > Cannot customize split behavior and merge policy for Infinispan partition handling > ---------------------------------------------------------------------------------- > > Key: WFLY-12881 > URL: https://issues.redhat.com/browse/WFLY-12881 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Critical > Fix For: 20.0.0.Beta1 > > > Currently, partition handling of an Infinispan cache is hard coded. When enabled, both reads and writes are denied on minority partitions (of a given segment) and, more critically, upon partition merge, no reconciliation of any data conflicts occurs. > Users need to be able to configure this, at least to support the built in read/write on split policy and the built-in merge policies. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4919) Long running query at kie-server startup

by Cristiano Nicolai (Jira)

[ https://issues.redhat.com/browse/DROOLS-4919?page=com.atlassian.jira.plug... ] Cristiano Nicolai commented on DROOLS-4919: ------------------------------------------- [~swiderski.maciej] correct, that was done as part of JBPM-8559. > Long running query at kie-server startup > ---------------------------------------- > > Key: DROOLS-4919 > URL: https://issues.redhat.com/browse/DROOLS-4919 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.28.0.Final > Reporter: Danny Rucker > Assignee: Maciej Swiderski > Priority: Major > > The following query is executed at start up of kie-server > ``` > select vil.processInstanceId, vil.processId, vil.id, vil.variableId, vil.value from VariableInstanceLog vil where vil.id in (select MAX(v.id) from VariableInstanceLog v group by v.variableId, v.processInstanceId) > ``` > This is causing some issues with getting kie-server to start up. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1860) Custom classloader in RpcDispatcher

by Todd Sandor (Jira)

[ https://issues.redhat.com/browse/JGRP-1860?page=com.atlassian.jira.plugin... ] Todd Sandor commented on JGRP-1860: ----------------------------------- We are a Redhat customer - this issue was raised on our behalf. We are not in the process of upgrading from JBoss EAP7.1 to 7.2 and the Groups version was changed from jgroups-3.6.14.Final-redhat-1.jar to jgroups-4.0.15.Final-redhat-00001.jar and at this point can not compile our application code (JGRP-1860). These changes do not seem to have been ported to JGroups 4 (7.2.0 uses 4.0.15.Final-redhat-00001.jar). Is it possible to get these ported to JGroups 4? I have raised case Redhat https://access.redhat.com/support/cases/#/case/02568685 for this. We have also found that org.jgroups.util.UUID is not backwards compatible between the above releases ...but it is not related to JGRP-1860 .. The issues are described in the above case. Cheers > Custom classloader in RpcDispatcher > ----------------------------------- > > Key: JGRP-1860 > URL: https://issues.redhat.com/browse/JGRP-1860 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.2.13 > Reporter: Dennis Reed > Assignee: Bela Ban > Priority: Major > Fix For: 3.4.5, 3.5 > > > RpcDispatcher is hard-coded to use JGroups' classloader when marshalling the users's custom objects over RPC. > RpcDispatcher uses Util.objectFromByteBuffer to unmarshall, which uses an ObjectInputStream. ObjectInputStream uses the classloader of its caller's class (Util). > RpcDispatcher does allow a custom marshaller to be used (implementing RpcDispatcher.Marshaller), but since Util.objectFromByteBuffer hard-codes the use of ObjectInputStream, a custom marshaller cannot simply set the classloader and then delegate back to the default JGroups code. > Util.objectFromBuffer should be enhanced to use a custom ObjectInputStream implementation that overrides resolveClass to use a custom classloader, and an API should be added to RpcDispatcher to pass in the classloader to use. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4955) [DMN Designer] Blog post - DMN Elements suggestions for FEEL code completion

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4955?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4955: ------------------------------------ Sprint: 2020 Week 04-06 (from Jan 20) > [DMN Designer] Blog post - DMN Elements suggestions for FEEL code completion > ---------------------------------------------------------------------------- > > Key: DROOLS-4955 > URL: https://issues.redhat.com/browse/DROOLS-4955 > Project: Drools > Issue Type: Task > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > > Create a blog post for https://issues.redhat.com/browse/BAPL-1480 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4781) Ability to enable shutdown operation for EmbeddedServer

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-4781?page=com.atlassian.jira.plug... ] Jean Francois Denise commented on WFCORE-4781: ---------------------------------------------- An embedded server can't be shutdown. Would be needed by the maven-plugin to kill a server started in background. Would be needed in general to implement termination strategy using CLI. > Ability to enable shutdown operation for EmbeddedServer > ------------------------------------------------------- > > Key: WFCORE-4781 > URL: https://issues.redhat.com/browse/WFCORE-4781 > Project: WildFly Core > Issue Type: Enhancement > Components: Embedded > Affects Versions: 11.0.0.Beta5 > Reporter: Jean Francois Denise > Assignee: James Perkins > Priority: Major > > Having the shutdown operation available for embedded is needed when the embedder process and embedded server shutdown phase are bound. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4485) Support for multiple security realms - Distributed Identities

by Carl Walker (Jira)

[ https://issues.redhat.com/browse/WFCORE-4485?page=com.atlassian.jira.plug... ] Carl Walker commented on WFCORE-4485: ------------------------------------- I have two use cases. In both cases, authentication and authorization info is kept in multiple places. (This isn't the "authenticate here / authorize there" scenario supported with aggregate.) 1) End users and admins credentials are located in different datastores (tables) but access the same resources. End users hit the first query. If that passes, they're authenticated and authorized. Admins fail on the first query, but succeed on the second. Business logic keeps the usernames unique across both stores. 2) Customer-maintained Active Directory and RDBMS-oriented "system accounts". Authentication is done against Active Directory for end users who have an identity in the enterprise system. System accounts will fail the AD check but will be picked up in a second RDBMS module. > Support for multiple security realms - Distributed Identities > ------------------------------------------------------------- > > Key: WFCORE-4485 > URL: https://issues.redhat.com/browse/WFCORE-4485 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Priority: Major > Labels: CD17-Deferred, EAP-CD19, Previous_RFE > Fix For: 11.0.0.Beta8 > > > By stacking LoginModules it was possible using PicketBox to attempt to authenticate using one remote store and if that failed try the next store in the list. > This RFE is to consider the use case where identities could be located across multiple stores and how they are aggregated together. > Additionally this use case should consider how the authorization information could be loaded from multiple sources and merged. > This RFE is not about fail over in the event of a realm being unavailable although it may be related. > This RFE is created as a result of comparing the differences between the PicketBox JAAS architecture and the Elytron architecture so I would not recommend this proceeds without some real world use cases identified. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12996) Upgrade Narayana to 5.10.3.Final

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/WFLY-12996?page=com.atlassian.jira.plugi... ] Michael Musgrove closed WFLY-12996. ----------------------------------- Release Notes Text: We only did a partial release so I will close this one an open another for when we do the next one (5.10.4.Final). Resolution: Won't Do > Upgrade Narayana to 5.10.3.Final > -------------------------------- > > Key: WFLY-12996 > URL: https://issues.redhat.com/browse/WFLY-12996 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Affects Versions: 19.0.0.Beta1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 19.0.0.Beta2 > > > Transactions component upgrade > https://issues.redhat.com/projects/JBTM/versions/12343377 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4977) [DMN Designer] Refactor DataObjectsServiceImpl to not duplicate logic from ParseHelper

by Daniel José dos Santos (Jira)

Daniel José dos Santos created DROOLS-4977: ---------------------------------------------- Summary: [DMN Designer] Refactor DataObjectsServiceImpl to not duplicate logic from ParseHelper Key: DROOLS-4977 URL: https://issues.redhat.com/browse/DROOLS-4977 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Daniel José dos Santos Assignee: Daniel José dos Santos Currently we have logic from [ParserHelper|https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-d...] duplicated in [DataObjectsServiceImpl|https://github.com/kiegroup/kie-wb-common/blob/969...] which may lead to some inconsistencies. `DataObjectsServiceImpl` should use `ParserHelper` and convert the result to a type that can be used by UI. This JIRA is derived from [RHDM-1145|https://issues.redhat.com/browse/RHDM-1145]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4976) Guided Decision Table Graphs do not work

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4976?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4976: --------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > Guided Decision Table Graphs do not work > ---------------------------------------- > > Key: DROOLS-4976 > URL: https://issues.redhat.com/browse/DROOLS-4976 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.32.0.Final > Reporter: Michael Anstis > Assignee: Toni Rikkola > Priority: Critical > Labels: drools-tools > > Users are no longer able to create Guided Decision Table Graphs. > A {{Parameter named 'analysisReportScreen' should be not null!}} error is thrown when trying to "open" an existing Guided Decision Table to the graph. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4976) Guided Decision Table Graphs do not work

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4976?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4976: --------------------------------- Priority: Critical (was: Major) > Guided Decision Table Graphs do not work > ---------------------------------------- > > Key: DROOLS-4976 > URL: https://issues.redhat.com/browse/DROOLS-4976 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.32.0.Final > Reporter: Michael Anstis > Assignee: Toni Rikkola > Priority: Critical > Labels: drools-tools > > Users are no longer able to create Guided Decision Table Graphs. > A {{Parameter named 'analysisReportScreen' should be not null!}} error is thrown when trying to "open" an existing Guided Decision Table to the graph. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 January 2020