February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-307) MP Fault Tolerance - unexpected behaviour @Fallback method calls with @CircuitBreaker

by Miroslav Novak (Jira)

Miroslav Novak created WFWIP-307: ------------------------------------ Summary: MP Fault Tolerance - unexpected behaviour @Fallback method calls with @CircuitBreaker Key: WFWIP-307 URL: https://issues.redhat.com/browse/WFWIP-307 Project: WildFly WIP Issue Type: Bug Components: MP Fault Tolerance Reporter: Miroslav Novak Assignee: Radoslav Husar MP FT does behave correctly in case when there is @CircuitBreaker, @Fallback, @Retry and @Asynchronous on service method. @CircuitBreaker does not get opened based on its configuration and @Fallback method is called with incorrect value. Test scenario: * Deploy MP FT service with: {code} @Asynchronous @Retry(retryOn = IOException.class) @CircuitBreaker(failOn = IOException.class, requestVolumeThreshold = 5, successThreshold = 3, delay = 2, delayUnit = ChronoUnit.SECONDS, failureRatio = 0.75) @Fallback(fallbackMethod = "processFallback") public CompletionStage<MyConnection> retryCircuitBreaker(int counter) throws IOException { System.out.println("retryCircuitBreaker - called - " + counter); if (counter % 4 != 0) { // 3/4 requests trigger IOException System.out.println("retryCircuitBreaker - called - " + counter + " throwing exception"); throw new IOException("Simulated IOException"); } System.out.println("retryCircuitBreaker - called - " + counter + " success"); return CompletableFuture.completedFuture(new MyConnection() { @Override public String getData() { return "Hello from @Retry @CircuitBreaker method" + counter; } }); } private CompletionStage<MyConnection> processFallback(int counter) { System.out.println("processFallback - returned url counter: " + counter); return CompletableFuture.completedFuture(new MyConnection() { @Override public String getData() { return "Fallback Hello" + counter; } }); } {code} * Sends 16 parallel requests. Every 4th requests pass (including 0th one is there modulo 4), and 12 invocations fail on IOException. * Try on more request and check that @Fallback method was called as circuit is open Expected result: Circuit gets opened and @Fallback method is called. Actual Result: Circuit is not opened and @Fallback method is called. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4863) Upgrade PicketBox to 5.0.3.Final-redhat-00006

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFCORE-4863?page=com.atlassian.jira.plug... ] Ilia Vassilev updated WFCORE-4863: ---------------------------------- Summary: Upgrade PicketBox to 5.0.3.Final-redhat-00006 (was: Upgrade picketbox to 5.0.3.Final-redhat-00006) > Upgrade PicketBox to 5.0.3.Final-redhat-00006 > --------------------------------------------- > > Key: WFCORE-4863 > URL: https://issues.redhat.com/browse/WFCORE-4863 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > Labels: downstream_dependency > > Branch: https://github.com/jbossas/redhat-picketbox/tree/5.0.x -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4863) Upgrade picketbox to 5.0.3.Final-redhat-00006

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFCORE-4863?page=com.atlassian.jira.plug... ] Ilia Vassilev moved JBEAP-18819 to WFCORE-4863: ----------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-4863 (was: JBEAP-18819) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Fix Version/s: (was: 7.3.1.GA) > Upgrade picketbox to 5.0.3.Final-redhat-00006 > --------------------------------------------- > > Key: WFCORE-4863 > URL: https://issues.redhat.com/browse/WFCORE-4863 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > Labels: downstream_dependency > > Branch: https://github.com/jbossas/redhat-picketbox/tree/5.0.x -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4959) Package name does not changes on copying of an existing package

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4959?page=com.atlassian.jira.plug... ] Toni Rikkola commented on DROOLS-4959: -------------------------------------- Unfortunately I doubt this will get fixed in the near future. The unfortunate workaround would be to git clone the project, change the packages and push changes back. > Package name does not changes on copying of an existing package > --------------------------------------------------------------- > > Key: DROOLS-4959 > URL: https://issues.redhat.com/browse/DROOLS-4959 > Project: Drools > Issue Type: Bug > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Attachments: step1.PNG, step2.PNG, step3.PNG, step4.PNG > > > After copying a package to a new one, all copied resources will remain referencing the existing one. > This becomes a bigger issue once you use guided rules, which their source cannot be edited. > Due to that, duplication alerts will be raised. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4862) NPE starting the server by using incorrect git repository configurations

by Yeray Borges Santana (Jira)

Yeray Borges Santana created WFCORE-4862: -------------------------------------------- Summary: NPE starting the server by using incorrect git repository configurations Key: WFCORE-4862 URL: https://issues.redhat.com/browse/WFCORE-4862 Project: WildFly Core Issue Type: Bug Reporter: Yeray Borges Santana Assignee: Yeray Borges Santana The standalone server can be configured to use a git repository as a persister to backup server configurations. When the server is started by using any of these configurations with incorrect values, the usage description is shown together with the following NPE trace that should not be there: {noformat} java.lang.NullPointerException at org.jboss.as.server@11.0.0.Beta10-SNAPSHOT//org.jboss.as.server.Main.main(Main.java:99) at org.jboss.modules.Module.run(Module.java:352) at org.jboss.modules.Module.run(Module.java:320) at org.jboss.modules.Main.main(Main.java:593) {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[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)

4 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)

4 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)

4 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)

4 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)

4 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2020