February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5101) rhdm 7 (v 7.5.1; eap 7.2; Drools 7.26; windows 10) FAIL - OutOfMemoryError

by Charles Herrick (Jira)

[ https://issues.redhat.com/browse/DROOLS-5101?page=com.atlassian.jira.plug... ] Charles Herrick commented on DROOLS-5101: ----------------------------------------- Workaround/fix: edit standalone.conf.bat to set Xmx and Xms to 3G under Windows 10 > rhdm 7 (v 7.5.1; eap 7.2; Drools 7.26; windows 10) FAIL - OutOfMemoryError > -------------------------------------------------------------------------- > > Key: DROOLS-5101 > URL: https://issues.redhat.com/browse/DROOLS-5101 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.26.0.Final > Reporter: Charles Herrick > Assignee: Mario Fusco > Priority: Critical > > 09:13:02,818 ERROR [org.kie.workbench.common.services.backend.builder.core.Builder] (default task-95) GC overhead limit exceeded: java.lang.OutOfMemoryError: GC overhead limit exceeded > 09:13:05,335 ERROR [stderr] (default task-95) java.lang.OutOfMemoryError: GC overhead limit exceeded -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5110) Rename/Change name of Space(s) from Decision Central

by Charles Herrick (Jira)

Charles Herrick created DROOLS-5110: --------------------------------------- Summary: Rename/Change name of Space(s) from Decision Central Key: DROOLS-5110 URL: https://issues.redhat.com/browse/DROOLS-5110 Project: Drools Issue Type: Feature Request Affects Versions: 7.26.0.Final Reporter: Charles Herrick Assignee: Mario Fusco Currently rename of spaces is not possible. Add new feature to (re)name an existing space in the Decision Central editor/dashboard. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5059) Verifier: GDST columns empty enumeration should be ignored

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5059?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-5059: --------------------------------- Description: Not sure how the problem GDST is created, but it looks like there is a scenario where the value list for column is empty instead of null and the empty String as value list triggered the Verifier to think the column is an enumeration column. > Verifier: GDST columns empty enumeration should be ignored > ---------------------------------------------------------- > > Key: DROOLS-5059 > URL: https://issues.redhat.com/browse/DROOLS-5059 > Project: Drools > Issue Type: Bug > Components: verifier > Affects Versions: 7.33.0.Final > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Not sure how the problem GDST is created, but it looks like there is a scenario where the value list for column is empty instead of null and the empty String as value list triggered the Verifier to think the column is an enumeration column. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11130) javax.security.enterprise.SecurityContext.isCallerInRole throws NullPointerException if the caller is not authenticated (New Java EE 8 Security)

by Moulali Shikalwadi (Jira)

[ https://issues.redhat.com/browse/WFLY-11130?page=com.atlassian.jira.plugi... ] Moulali Shikalwadi reassigned WFLY-11130: ----------------------------------------- Assignee: Moulali Shikalwadi > javax.security.enterprise.SecurityContext.isCallerInRole throws NullPointerException if the caller is not authenticated (New Java EE 8 Security) > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-11130 > URL: https://issues.redhat.com/browse/WFLY-11130 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 14.0.1.Final > Reporter: Instantiation Exception > Assignee: Moulali Shikalwadi > Priority: Major > > I tried to use new Java EE 8 Security API and noticed that javax.security.enterprise.SecurityContext.isCallerInRole throws NullPointerException if the caller is not authenticated. But according to JavaDoc it should return false in this situation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5109) Replace verifier DataType with kie-soup DataType

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5109: ----------------------------------- Summary: Replace verifier DataType with kie-soup DataType Key: DROOLS-5109 URL: https://issues.redhat.com/browse/DROOLS-5109 Project: Drools Issue Type: Task Components: Guided Decision Table Editor Reporter: Jozef Marko Assignee: Jozef Marko Idea for this code enhancement emerged during https://github.com/kiegroup/drools-wb/pull/1311/files PR review. We have two instances of DataType, while we can replace the first one with the second one. - https://github.com/kiegroup/drools/blob/master/drools-verifier/drools-ver... - https://github.com/kiegroup/kie-soup/blob/master/kie-soup-project-datamod... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5059) Verifier: GDST columns empty enumeration should be ignored

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5059?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5059: -------------------------------- Affects Version/s: 7.33.0.Final > Verifier: GDST columns empty enumeration should be ignored > ---------------------------------------------------------- > > Key: DROOLS-5059 > URL: https://issues.redhat.com/browse/DROOLS-5059 > Project: Drools > Issue Type: Bug > Components: verifier > Affects Versions: 7.33.0.Final > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5085) list of triggered rules when executing test scenario

by Werner Van Herrewegen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5085?page=com.atlassian.jira.plug... ] Werner Van Herrewegen commented on DROOLS-5085: ----------------------------------------------- indeed, I missed this feature. ticket can be closed kr, Werner > list of triggered rules when executing test scenario > ---------------------------------------------------- > > Key: DROOLS-5085 > URL: https://issues.redhat.com/browse/DROOLS-5085 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Werner Van Herrewegen > Assignee: Daniele Zonca > Priority: Major > Attachments: Screenshot from 2020-02-20 18-14-48.png, Screenshot from 2020-02-20 18-15-19.png > > > As a business user running a test scenario, I would like to know what rules triggered, so I know where to look when the test fails. > technical implementation suggestion: > the log window beneath the test is a good place. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13164) When "corrupted" public key is supplied to server, user is not informed

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-13164?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFLY-13164: ----------------------------------------- I think Critical would be a more appropriate priority rather than requesting all releases are delayed. We do want to fix this ASAP but we are in a state where a deployment that would not work remains in a state where it would not work the only difference is in the error reporting. > When "corrupted" public key is supplied to server, user is not informed > ----------------------------------------------------------------------- > > Key: WFLY-13164 > URL: https://issues.redhat.com/browse/WFLY-13164 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Affects Versions: 19.0.0.Beta2, 20.0.0.Beta1 > Reporter: Jan Kasik > Assignee: Darran Lofthouse > Priority: Blocker > Attachments: CorruptedKeyTest.war > > > When corrupted public key (a valid key cannot be extracted from the string value) is supplied to JWT verifier, user is not informed since there is no error message in log and clients receives 401 status code in response instead of an error code of 500. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5108) KieHelper.build is very slow on Drools 6.4.0.Final

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5108?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-5108. --------------------------------- Resolution: Out of Date 6.4.0.Final is 4 years old and of course we cannot provide community support for a so old release. Please try with a more recent one. Also claiming that X is "slow" while doing Y is not something workable. First of all you should provide a complete reproducer to allow us to benchmark and profile your specific situation. Second generically saying that it is "slow" isn't an objective measure. What are your expectations? What is a value acceptable for you and under which threshold you will stop considering this "slow"? > KieHelper.build is very slow on Drools 6.4.0.Final > -------------------------------------------------- > > Key: DROOLS-5108 > URL: https://issues.redhat.com/browse/DROOLS-5108 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Ravi M > Assignee: Mario Fusco > Priority: Major > > Tried build with 230 rules, it is taking nearly 10 seconds > {code:java} > org.kie.internal.utils.KieHelper kieHelper = new org.kie.internal.utils.KieHelper(); > kieHelper.setClassLoader(this.getClass().getClassLoader()); > kieHelper.addContent( drlContent, ResourceType.DRL ); > Results res = kieHelper.verify(); > if ( res.hasMessages( Message.Level.ERROR ) ) { > throw new DroolsCompilationException("Exception while compiling rule "); > } > if ( kbConf == null ) { > kbConf = KieServices.Factory.get().newKieBaseConfiguration(); > } > kbConf.setOption( EqualityBehaviorOption.EQUALITY ); > KieBase kieBase = kieHelper.build( kbConf ); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5108) KieHelper.build is very slow on Drools 6.4.0.Final

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5108?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5108: -------------------------------- Sprint: 2020 Week 07-09 (from Feb 10) > KieHelper.build is very slow on Drools 6.4.0.Final > -------------------------------------------------- > > Key: DROOLS-5108 > URL: https://issues.redhat.com/browse/DROOLS-5108 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Ravi M > Assignee: Mario Fusco > Priority: Major > > Tried build with 230 rules, it is taking nearly 10 seconds > {code:java} > org.kie.internal.utils.KieHelper kieHelper = new org.kie.internal.utils.KieHelper(); > kieHelper.setClassLoader(this.getClass().getClassLoader()); > kieHelper.addContent( drlContent, ResourceType.DRL ); > Results res = kieHelper.verify(); > if ( res.hasMessages( Message.Level.ERROR ) ) { > throw new DroolsCompilationException("Exception while compiling rule "); > } > if ( kbConf == null ) { > kbConf = KieServices.Factory.get().newKieBaseConfiguration(); > } > kbConf.setOption( EqualityBehaviorOption.EQUALITY ); > KieBase kieBase = kieHelper.build( kbConf ); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 February 2020