June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4131) Can't use "is contained in the list" for Integer field

by Yevgeniy Fomin (Jira)

[ https://issues.jboss.org/browse/DROOLS-4131?page=com.atlassian.jira.plugi... ] Yevgeniy Fomin updated DROOLS-4131: ----------------------------------- Attachment: ResultAfterFirstPR.webm > Can't use "is contained in the list" for Integer field > ------------------------------------------------------ > > Key: DROOLS-4131 > URL: https://issues.jboss.org/browse/DROOLS-4131 > Project: Drools > Issue Type: Bug > Components: Guided Template Editor > Affects Versions: 7.23.0.Final > Reporter: Yevgeniy Fomin > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > Attachments: ResultAfterFirstPR.webm, Screenshot from 2019-06-05 16-04-55.png, Screenshot from 2019-06-05 16-05-17.png, Screenshot from 2019-06-05 16-06-23.png, Screenshot from 2019-06-05 16-06-50.png > > > Can't use "Template key" as a list when using option "is contained in the (comma separated) list" for Integer field of Data Object in Guided Rule Templates -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12167) Memory leak in metrics in standalone-ha configuration

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12167?page=com.atlassian.jira.plugin... ] Radoslav Husar reassigned WFLY-12167: ------------------------------------- Assignee: Richard Opalka (was: Paul Ferraro) This is most likely a MSC issue, Richard O. is looking into it. > Memory leak in metrics in standalone-ha configuration > ----------------------------------------------------- > > Key: WFLY-12167 > URL: https://issues.jboss.org/browse/WFLY-12167 > Project: WildFly > Issue Type: Bug > Components: Clustering, MP Metrics, MSC > Affects Versions: 16.0.0.Final > Reporter: Bernd Stolle > Assignee: Richard Opalka > Priority: Blocker > Labels: memoryleak > Attachments: Screenshot 2019-06-06 at 11.07.00.png > > > When started in standalone HA configuration every request to the recently added metrics endpoint ({{<management-if>:9990/metrics}}) lead to an increase in memory consumption until the JVM is slowed down significantly by GC to a point where even the requests to {{/health}} fail within a reasonable timeout (2s) and untlimately lead to OOM. > The same issue does not occur when WildFly is started in the default standalone configuration (non HA). > I can provide a (compressed) heap dump if required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12167) Memory leak in metrics in standalone-ha configuration

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12167?page=com.atlassian.jira.plugin... ] Radoslav Husar edited comment on WFLY-12167 at 6/6/19 8:18 AM: --------------------------------------------------------------- This is most likely a MSC issue, Richard O. is testing a fix now. was (Author: rhusar): This is most likely a MSC issue, Richard O. is looking into it. > Memory leak in metrics in standalone-ha configuration > ----------------------------------------------------- > > Key: WFLY-12167 > URL: https://issues.jboss.org/browse/WFLY-12167 > Project: WildFly > Issue Type: Bug > Components: Clustering, MP Metrics, MSC > Affects Versions: 16.0.0.Final > Reporter: Bernd Stolle > Assignee: Richard Opalka > Priority: Blocker > Labels: memoryleak > Attachments: Screenshot 2019-06-06 at 11.07.00.png > > > When started in standalone HA configuration every request to the recently added metrics endpoint ({{<management-if>:9990/metrics}}) lead to an increase in memory consumption until the JVM is slowed down significantly by GC to a point where even the requests to {{/health}} fail within a reasonable timeout (2s) and untlimately lead to OOM. > The same issue does not occur when WildFly is started in the default standalone configuration (non HA). > I can provide a (compressed) heap dump if required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12167) Memory leak in metrics in standalone-ha configuration

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12167?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12167: ---------------------------------- Component/s: MSC > Memory leak in metrics in standalone-ha configuration > ----------------------------------------------------- > > Key: WFLY-12167 > URL: https://issues.jboss.org/browse/WFLY-12167 > Project: WildFly > Issue Type: Bug > Components: Clustering, MP Metrics, MSC > Affects Versions: 16.0.0.Final > Reporter: Bernd Stolle > Assignee: Paul Ferraro > Priority: Blocker > Labels: memoryleak > Attachments: Screenshot 2019-06-06 at 11.07.00.png > > > When started in standalone HA configuration every request to the recently added metrics endpoint ({{<management-if>:9990/metrics}}) lead to an increase in memory consumption until the JVM is slowed down significantly by GC to a point where even the requests to {{/health}} fail within a reasonable timeout (2s) and untlimately lead to OOM. > The same issue does not occur when WildFly is started in the default standalone configuration (non HA). > I can provide a (compressed) heap dump if required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4140) Global's method names starting with word modify are truncated

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-4140?page=com.atlassian.jira.plugi... ] Luca Molteni updated DROOLS-4140: --------------------------------- Sprint: 2019 Week 23-25 > Global's method names starting with word modify are truncated > ------------------------------------------------------------- > > Key: DROOLS-4140 > URL: https://issues.jboss.org/browse/DROOLS-4140 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.21.0.Final > Environment: FLOW_DSL, PATTERN_DSL > Reporter: Peter Martinovič > Assignee: Luca Molteni > Priority: Major > Attachments: DROOLS-4140-test.patch > > > If global's method name starts with modify, the first character of the method name is lost during code generation. > Compilation then fails. > {code:java} > org.drools.model.Rule rule = D.rule("Rule 1").build(D.on(var_g).execute((g) -> { > g.odifyIsTheFirstWordInTheMethodName(); > })); > {code} > (It does not seem to happen with method names starting with keywords insert, delete.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4140) Global's method names starting with word modify are truncated

by Peter Martinovič (Jira)

[ https://issues.jboss.org/browse/DROOLS-4140?page=com.atlassian.jira.plugi... ] Peter Martinovič updated DROOLS-4140: ------------------------------------- Description: If global's method name starts with modify, the first character of the method name is lost during code generation. Compilation then fails. {code:java} org.drools.model.Rule rule = D.rule("Rule 1").build(D.on(var_g).execute((g) -> { g.odifyIsTheFirstWordInTheMethodName(); })); {code} (It does not seem to happen with method names starting with keywords insert, delete.) was: If global's method name starts with modify, the first character of the method name is lost during code generation. Compilation then fails. {code:java} org.drools.model.Rule rule = D.rule("Rule 1").build(D.on(var_g).execute((g) -> { g.odifyIsTheFirstWordInTheMethodName(); })); {code} > Global's method names starting with word modify are truncated > ------------------------------------------------------------- > > Key: DROOLS-4140 > URL: https://issues.jboss.org/browse/DROOLS-4140 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.21.0.Final > Environment: FLOW_DSL, PATTERN_DSL > Reporter: Peter Martinovič > Assignee: Luca Molteni > Priority: Major > Attachments: DROOLS-4140-test.patch > > > If global's method name starts with modify, the first character of the method name is lost during code generation. > Compilation then fails. > {code:java} > org.drools.model.Rule rule = D.rule("Rule 1").build(D.on(var_g).execute((g) -> { > g.odifyIsTheFirstWordInTheMethodName(); > })); > {code} > (It does not seem to happen with method names starting with keywords insert, delete.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4140) Global's method names starting with word modify are truncated

by Peter Martinovič (Jira)

[ https://issues.jboss.org/browse/DROOLS-4140?page=com.atlassian.jira.plugi... ] Peter Martinovič updated DROOLS-4140: ------------------------------------- Summary: Global's method names starting with word modify are truncated (was: Global) > Global's method names starting with word modify are truncated > ------------------------------------------------------------- > > Key: DROOLS-4140 > URL: https://issues.jboss.org/browse/DROOLS-4140 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.21.0.Final > Environment: FLOW_DSL, PATTERN_DSL > Reporter: Peter Martinovič > Assignee: Luca Molteni > Priority: Major > Attachments: DROOLS-4140-test.patch > > > If global's method name starts with modify, the first character of the method name is lost during code generation. > Compilation then fails. > {code:java} > org.drools.model.Rule rule = D.rule("Rule 1").build(D.on(var_g).execute((g) -> { > g.odifyIsTheFirstWordInTheMethodName(); > })); > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4140) Global's method names starting with word modify are truncated

by Peter Martinovič (Jira)

[ https://issues.jboss.org/browse/DROOLS-4140?page=com.atlassian.jira.plugi... ] Peter Martinovič updated DROOLS-4140: ------------------------------------- Attachment: DROOLS-4140-test.patch > Global's method names starting with word modify are truncated > ------------------------------------------------------------- > > Key: DROOLS-4140 > URL: https://issues.jboss.org/browse/DROOLS-4140 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.21.0.Final > Environment: FLOW_DSL, PATTERN_DSL > Reporter: Peter Martinovič > Assignee: Luca Molteni > Priority: Major > Attachments: DROOLS-4140-test.patch > > > If global's method name starts with modify, the first character of the method name is lost during code generation. > Compilation then fails. > {code:java} > org.drools.model.Rule rule = D.rule("Rule 1").build(D.on(var_g).execute((g) -> { > g.odifyIsTheFirstWordInTheMethodName(); > })); > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4140) Global

by Peter Martinovič (Jira)

[ https://issues.jboss.org/browse/DROOLS-4140?page=com.atlassian.jira.plugi... ] Peter Martinovič updated DROOLS-4140: ------------------------------------- Description: If global's method name starts with modify, the first character of the method name is lost during code generation. Compilation then fails. {code:java} org.drools.model.Rule rule = D.rule("Rule 1").build(D.on(var_g).execute((g) -> { g.odifyIsTheFirstWordInTheMethodName(); })); {code} was:I will provide details ASAP, I wanted to have the issue number to create reproducer Steps to Reproduce: Apply the attached patch. Run org.drools.modelcompiler.CompilerTest#testGlobalMethodNameStartingWithModify Summary: Global (was: Executable rule model - first char of global's method name is lost during compilation) Environment: FLOW_DSL, PATTERN_DSL > Global > ------ > > Key: DROOLS-4140 > URL: https://issues.jboss.org/browse/DROOLS-4140 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.21.0.Final > Environment: FLOW_DSL, PATTERN_DSL > Reporter: Peter Martinovič > Assignee: Luca Molteni > Priority: Major > > If global's method name starts with modify, the first character of the method name is lost during code generation. > Compilation then fails. > {code:java} > org.drools.model.Rule rule = D.rule("Rule 1").build(D.on(var_g).execute((g) -> { > g.odifyIsTheFirstWordInTheMethodName(); > })); > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12167) Memory leak in metrics in standalone-ha configuration

by Bernd Stolle (Jira)

[ https://issues.jboss.org/browse/WFLY-12167?page=com.atlassian.jira.plugin... ] Bernd Stolle commented on WFLY-12167: ------------------------------------- [~jmesnil] Sorry i missed your comment, the link to the heap dump is here: https://cloud.0xcafec0.de/index.php/s/8dKCZqm237FEJmy in case you still need it. > Memory leak in metrics in standalone-ha configuration > ----------------------------------------------------- > > Key: WFLY-12167 > URL: https://issues.jboss.org/browse/WFLY-12167 > Project: WildFly > Issue Type: Bug > Components: Clustering, MP Metrics > Affects Versions: 16.0.0.Final > Reporter: Bernd Stolle > Assignee: Paul Ferraro > Priority: Blocker > Labels: memoryleak > Attachments: Screenshot 2019-06-06 at 11.07.00.png > > > When started in standalone HA configuration every request to the recently added metrics endpoint ({{<management-if>:9990/metrics}}) lead to an increase in memory consumption until the JVM is slowed down significantly by GC to a point where even the requests to {{/health}} fail within a reasonable timeout (2s) and untlimately lead to OOM. > The same issue does not occur when WildFly is started in the default standalone configuration (non HA). > I can provide a (compressed) heap dump if required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 June 2019