[JBoss JIRA] (WFLY-12937) Expired distributed web sessions/SFSBs not properly removed following rehash
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-12937:
-----------------------------------
Summary: Expired distributed web sessions/SFSBs not properly removed following rehash
Key: WFLY-12937
URL: https://issues.redhat.com/browse/WFLY-12937
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 18.0.1.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
On topology change, changes to primary session ownership determine when a given member should schedule expiration of a given session, or cancel a scheduled expiration of a previously owned session. Primary ownership is determined by 2 components: the key partitioner and a consistent hash. The key partitioner determines which the segment to which a given key is assigned. A consistent hash determines which member is the primary owner of a given segment.
The logic for determining primary ownership changes currently uses the wrong key partitioner. Currently, we use the partitioner from the cache configuration. However, when grouping is enabled (which is the case for web sessions and SFSBs), this parititioner is wrapped by a GroupPartitioner at runtime. That is the one we need.
This results in expired web sessions/SFSBs remaining in memory, potentially indefinitely.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-4555) functionDefinition parameter with trailing space causes NPE
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-4555?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-4555:
-----------------------------------
Tester: Tibor Zimanyi
Story Points: 2
Sprint: 2020 Week 01-03 (from Dec 30)
> functionDefinition parameter with trailing space causes NPE
> -----------------------------------------------------------
>
> Key: DROOLS-4555
> URL: https://issues.redhat.com/browse/DROOLS-4555
> Project: Drools
> Issue Type: Bug
> Reporter: Jonas Tamimi
> Assignee: Matteo Mortari
> Priority: Major
>
> Hi,
> this is my first issue, so I hope I did everything right. We have been using version 7.21.0.Final of Drools for the last few months. A few weeks ago we switched to the latest version and could not import a few of our decision models (.dmn) anymore. According to our own research the bug seems to be present since 7.22.0.t042 and is still present in the latest snapshot.
> This is the relevant logging output: [https://gist.github.com/oas/ec0f70585411d8c3f0266b7d2fd02ebc|https://gist...]
> I tried to narrow down the exception and it seems to be in the method {{checkVariableName}} of {{org.kie.dmn.feel.parser.feel11.FEELParser}}. {{errorChecker.hasErrors()}} is false, but it is not catched by the if statement in line 111. Because of this, {{errorChecker.getErrors()}} returns null instead of a {{List<FEELEvent>}}.
> The method {{checkVariableName}} in {{org.kie.dmn.core.compiler.DMNCompilerHelper}}, assumes that a list will be returned and calls {{isEmpty()}}. This throws the {{NullPointerException}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-4903) In constraints fail to compile if negated or inside a forall pattern
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-4903?page=com.atlassian.jira.plug... ]
Mario Fusco resolved DROOLS-4903.
---------------------------------
Resolution: Done
Fixed by https://github.com/kiegroup/drools/commit/9ac0e309d716606c8b07085386d13fd...
> In constraints fail to compile if negated or inside a forall pattern
> --------------------------------------------------------------------
>
> Key: DROOLS-4903
> URL: https://issues.redhat.com/browse/DROOLS-4903
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.31.0.Final
> Reporter: Matteo Casalino
> Assignee: Mario Fusco
> Priority: Major
> Attachments: in-constraint-negation.tgz
>
>
> It appears that the KieBuilder fails to compile the following pattern:
> {noformat}
> Pojo(!(x in (1,2,3)))
> {noformat}
> returning the following error:
> {noformat}
> Error Messages:
> Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0
> text=Unable to Analyse Expression !(x in (1,2,3)):
> [Error: unexpected token: ,2]
> [Near : {... !(x in (1,2,3)) ....}]
> {noformat}
> Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile:
> {noformat}
> forall(Pojo(y==42, x in (1,2,3)))
> {noformat}
> with the following error:
> {noformat}
> Error Messages:
> Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0
> text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)):
> [Error: unexpected token: ,2]
> [Near : {... !(y==42) || !(x in (1,2,3)) ....}]
> {noformat}
> The latter is likely a consequence of the negation introduced by [DROOLS-4632], [DROOLS-4633]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-4555) functionDefinition parameter with trailing space causes NPE
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-4555?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-4555:
-----------------------------------
Summary: functionDefinition parameter with trailing space causes NPE (was: Importing DMN model causes NullPointerException)
> functionDefinition parameter with trailing space causes NPE
> -----------------------------------------------------------
>
> Key: DROOLS-4555
> URL: https://issues.redhat.com/browse/DROOLS-4555
> Project: Drools
> Issue Type: Bug
> Reporter: Jonas Tamimi
> Assignee: Matteo Mortari
> Priority: Major
>
> Hi,
> this is my first issue, so I hope I did everything right. We have been using version 7.21.0.Final of Drools for the last few months. A few weeks ago we switched to the latest version and could not import a few of our decision models (.dmn) anymore. According to our own research the bug seems to be present since 7.22.0.t042 and is still present in the latest snapshot.
> This is the relevant logging output: [https://gist.github.com/oas/ec0f70585411d8c3f0266b7d2fd02ebc|https://gist...]
> I tried to narrow down the exception and it seems to be in the method {{checkVariableName}} of {{org.kie.dmn.feel.parser.feel11.FEELParser}}. {{errorChecker.hasErrors()}} is false, but it is not catched by the if statement in line 111. Because of this, {{errorChecker.getErrors()}} returns null instead of a {{List<FEELEvent>}}.
> The method {{checkVariableName}} in {{org.kie.dmn.core.compiler.DMNCompilerHelper}}, assumes that a list will be returned and calls {{isEmpty()}}. This throws the {{NullPointerException}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months