[JBoss JIRA] (DROOLS-4896) Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALLOWED
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-4896?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-4896:
--------------------------------
Sprint: 2020 Week 01-03 (from Dec 30)
> Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALLOWED
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-4896
> URL: https://issues.redhat.com/browse/DROOLS-4896
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.14.0.Final, 7.26.0.Final, 7.31.0.Final
> Reporter: Hiroko Miura
> Assignee: Mario Fusco
> Priority: Major
> Labels: support
> Attachments: bigdecimal-accumulate-test.zip
>
>
> Regarding accumulate, min function with BigDecimal does not work as expected when drools.propertySpecific is "ALLOWED".
> The following rule worked with BRMS6.1.4(6.2.0.Final-redhat-13).
> {noformat}
> rule "rule1_BigDecimal"
> agenda-group "BigDecimal"
> when
> accumulate( Fact( $bdVal: bdVal), $minVal : min($bdVal))
> accumulate( Fact( $bdVal2: bdVal, $bdVal2 > $minVal), $minVal2 : min($bdVal2))
>
> $minFact: Fact( bdVal == new BigDecimal($minVal.intValue()))
> $minFact2: Fact( bdVal == new BigDecimal($minVal2.intValue()))
> then
> ...
> end
> {noformat}
> But after upgrading to RHPAM 7 and setting drools.propertySpecific=ALLOWED, this does not work.
> i.e. rule fires one more time than expected even though there is only one fact at the last iteration.
> This does not happen at least with Long type.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (AG-135) Connection doesn't release.
by bingo chen (Jira)
bingo chen created AG-135:
-----------------------------
Summary: Connection doesn't release.
Key: AG-135
URL: https://issues.redhat.com/browse/AG-135
Project: Agroal
Issue Type: Bug
Components: narayana
Affects Versions: 1.7
Reporter: bingo chen
Assignee: Luis Barreiro
We use narayana as our application JTA component. Through some tests we found an issue that database connection which related to recovery doesn't release.
The narayana use periodic recovery works; During each recovery job execution, the XADataSource is re-established, the connection obtained from the XADataSource doesn't release after recovery job finished, the connections are released only after the GC is executed.
Is this a problem or am I misconfiguring some settings?
the narayana version is 5.10.1.final
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (AG-134) Some issues in when use MSSQL SQLServerXADataSource
by bingo chen (Jira)
[ https://issues.redhat.com/browse/AG-134?page=com.atlassian.jira.plugin.sy... ]
bingo chen commented on AG-134:
-------------------------------
By looking at the source code, we resolved this issue by put 'URL' property to jdbc properties.
Can some one close this issue, thank you.
> Some issues in when use MSSQL SQLServerXADataSource
> ---------------------------------------------------
>
> Key: AG-134
> URL: https://issues.redhat.com/browse/AG-134
> Project: Agroal
> Issue Type: Enhancement
> Components: pool
> Affects Versions: 1.7
> Reporter: bingo chen
> Assignee: Luis Barreiro
> Priority: Major
>
> We use MSSQL as our data base server and use 'com.microsoft.sqlserver.jdbc.SQLServerXADataSource' as driver class.
> Here some issues occured, the SQLServerXADataSource url property name is 'URL' not 'url', so we can't connect the data base server.
> Environments:
> 1.JDBC driver is 'mssql-jdbc.7.2.2.jre8'
> <dependency>
> <groupId>com.microsoft.sqlserver</groupId>
> <artifactId>mssql-jdbc</artifactId>
> <version>7.2.2.jre8</version>
> </dependency>
> 2.Agroal 1.7
> <dependency>
> <groupId>io.agroal</groupId>
> <artifactId>agroal-api</artifactId>
> <version>1.7</version>
> </dependency>
> <dependency>
> <groupId>io.agroal</groupId>
> <artifactId>agroal-pool</artifactId>
> <version>1.7</version>
> </dependency>
> <dependency>
> <groupId>io.agroal</groupId>
> <artifactId>agroal-narayana</artifactId>
> <version>1.7</version>
> </dependency>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4898) Accumulates: min does not work after retracting fact.
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-4898:
------------------------------------
Summary: Accumulates: min does not work after retracting fact.
Key: DROOLS-4898
URL: https://issues.redhat.com/browse/DROOLS-4898
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.31.0.Final, 7.26.0.Final
Reporter: Hiroko Miura
Assignee: Mario Fusco
The following rules does not work with specific facts.
{noformat}
rule "rule1_long"
when
accumulate( Fact( $longVal: longVal), $minVal : min($longVal))
accumulate( Fact( $longVal2: longVal, $longVal2 > $minVal), $minVal2 : min($longVal2))
$minFact: Fact( longVal == $minVal)
$minFact2: Fact( longVal == $minVal2)
then
System.out.println("Rule ["+kcontext.getRule().getName()+ "] fires!");
Long $diff = (Long)$minVal2 - (Long)$minVal;
$minFact2.setDiff($diff);
// update($minFact2);
String errmsg = $diff == 0? " !!!!! ERROR !!!!!" : "";
System.out.println( drools.getRule().getName() + " diff：" + $minFact2.getLongVal() + " - " + $minFact.getLongVal() + " = " + $diff + errmsg);
System.out.println("\tretract <= "+$minFact );
retract($minFact);
end
{noformat}
There seems to be 2 kind of issues (root cause might be same though).
- 2nd accumulate return same min value with 1st one.
- rule fire count is less than expected.
This does not work with specific set of facts, but works with another set of facts.
If update is called for the fact like above commented out line, this does not happen.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4896) Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALLOWED
by Hiroko Miura (Jira)
[ https://issues.redhat.com/browse/DROOLS-4896?page=com.atlassian.jira.plug... ]
Hiroko Miura updated DROOLS-4896:
---------------------------------
Description:
Regarding accumulate, min function with BigDecimal does not work as expected when drools.propertySpecific is "ALLOWED".
The following rule worked with BRMS6.1.4(6.2.0.Final-redhat-13).
{noformat}
rule "rule1_BigDecimal"
agenda-group "BigDecimal"
when
accumulate( Fact( $bdVal: bdVal), $minVal : min($bdVal))
accumulate( Fact( $bdVal2: bdVal, $bdVal2 > $minVal), $minVal2 : min($bdVal2))
$minFact: Fact( bdVal == new BigDecimal($minVal.intValue()))
$minFact2: Fact( bdVal == new BigDecimal($minVal2.intValue()))
then
...
end
{noformat}
But after upgrading to RHPAM 7 and setting drools.propertySpecific=ALLOWED, this does not work.
i.e. rule fires one more time than expected even though there is only one fact at the last iteration.
This does not happen at least with Long type.
was:
Regarding accumulate, min function with BigDecimal does not work as expected when drools.propertySpecific is "ALLOWED".
The following rule worked with BRMS6.1.4(6.2.0.Final-redhat-13).
{noformat}
rule "rule1_BigDecimal"
agenda-group "BigDecimal"
when
accumulate( Fact( $bdVal: bdVal), $minVal : min($bdVal))
accumulate( Fact( $bdVal2: bdVal, $bdVal2 > $minVal), $minVal2 : min($bdVal2))
$minFact: Fact( bdVal == new BigDecimal($minVal.intValue()))
$minFact2: Fact( bdVal == new BigDecimal($minVal2.intValue()))
then
...
end
{noformat}
But after upgrading to RHPAM 7 and setting drools.propertySpecific=ALLOWED, this does not work.
i.e. rule fires one more time than expected even though there is only one fact at the last iteration.
> Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALLOWED
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-4896
> URL: https://issues.redhat.com/browse/DROOLS-4896
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.14.0.Final, 7.26.0.Final, 7.31.0.Final
> Reporter: Hiroko Miura
> Assignee: Mario Fusco
> Priority: Major
> Labels: support
> Attachments: bigdecimal-accumulate-test.zip
>
>
> Regarding accumulate, min function with BigDecimal does not work as expected when drools.propertySpecific is "ALLOWED".
> The following rule worked with BRMS6.1.4(6.2.0.Final-redhat-13).
> {noformat}
> rule "rule1_BigDecimal"
> agenda-group "BigDecimal"
> when
> accumulate( Fact( $bdVal: bdVal), $minVal : min($bdVal))
> accumulate( Fact( $bdVal2: bdVal, $bdVal2 > $minVal), $minVal2 : min($bdVal2))
>
> $minFact: Fact( bdVal == new BigDecimal($minVal.intValue()))
> $minFact2: Fact( bdVal == new BigDecimal($minVal2.intValue()))
> then
> ...
> end
> {noformat}
> But after upgrading to RHPAM 7 and setting drools.propertySpecific=ALLOWED, this does not work.
> i.e. rule fires one more time than expected even though there is only one fact at the last iteration.
> This does not happen at least with Long type.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4897) Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALLOWED
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-4897:
------------------------------------
Summary: Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALLOWED
Key: DROOLS-4897
URL: https://issues.redhat.com/browse/DROOLS-4897
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.14.0.Final, 7.26.0.Final, 7.31.0.Final
Reporter: Hiroko Miura
Assignee: Mario Fusco
Attachments: bigdecimal-accumulate-test.zip
Regarding accumulate, min function with BigDecimal does not work as expected when drools.propertySpecific is "ALLOWED".
The following rule worked with BRMS6.1.4(6.2.0.Final-redhat-13).
{noformat}
rule "rule1_BigDecimal"
agenda-group "BigDecimal"
when
accumulate( Fact( $bdVal: bdVal), $minVal : min($bdVal))
accumulate( Fact( $bdVal2: bdVal, $bdVal2 > $minVal), $minVal2 : min($bdVal2))
$minFact: Fact( bdVal == new BigDecimal($minVal.intValue()))
$minFact2: Fact( bdVal == new BigDecimal($minVal2.intValue()))
then
...
end
{noformat}
But after upgrading to RHPAM 7 and setting drools.propertySpecific=ALLOWED, this does not work.
i.e. rule fires one more time than expected even though there is only one fact at the last iteration.
This does not happen at least with Long type.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4896) Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALLOWED
by Hiroko Miura (Jira)
[ https://issues.redhat.com/browse/DROOLS-4896?page=com.atlassian.jira.plug... ]
Hiroko Miura updated DROOLS-4896:
---------------------------------
Description:
Regarding accumulate, min function with BigDecimal does not work as expected when drools.propertySpecific is "ALLOWED".
The following rule worked with BRMS6.1.4(6.2.0.Final-redhat-13).
{noformat}
rule "rule1_BigDecimal"
agenda-group "BigDecimal"
when
accumulate( Fact( $bdVal: bdVal), $minVal : min($bdVal))
accumulate( Fact( $bdVal2: bdVal, $bdVal2 > $minVal), $minVal2 : min($bdVal2))
$minFact: Fact( bdVal == new BigDecimal($minVal.intValue()))
$minFact2: Fact( bdVal == new BigDecimal($minVal2.intValue()))
then
...
end
{noformat}
But after upgrading to RHPAM 7 and setting drools.propertySpecific=ALLOWED, this does not work.
i.e. rule fires one more time than expected even though there is only one fact at the last iteration.
was:
Regarding accumulate, min function with BigDecimal does not work as expected when drools.propertySpecific is "ALLOWED".
The following rule worked with BRMS6.1.4(6.2.0.Final-redhat-13).
{noformat}
rule "rule1_BigDecimal"
agenda-group "BigDecimal"
when
accumulate( Fact( $bdVal: bdVal), $minVal : min($bdVal))
accumulate( Fact( $bdVal2: bdVal, $bdVal2 > $minVal), $minVal2 : min($bdVal2))
$minFact: Fact( bdVal == new BigDecimal($minVal.intValue()))
$minFact2: Fact( bdVal == new BigDecimal($minVal2.intValue()))
then
...
end
{noformat}
But after upgrading to RHPAM 7 and setting drools.propertySpecific=ALWAYS, this does not work.
i.e. rule fires one more time than expected even though there is only one fact at the last iteration.
> Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALLOWED
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-4896
> URL: https://issues.redhat.com/browse/DROOLS-4896
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.14.0.Final, 7.26.0.Final, 7.31.0.Final
> Reporter: Hiroko Miura
> Assignee: Mario Fusco
> Priority: Major
> Labels: support
> Attachments: bigdecimal-accumulate-test.zip
>
>
> Regarding accumulate, min function with BigDecimal does not work as expected when drools.propertySpecific is "ALLOWED".
> The following rule worked with BRMS6.1.4(6.2.0.Final-redhat-13).
> {noformat}
> rule "rule1_BigDecimal"
> agenda-group "BigDecimal"
> when
> accumulate( Fact( $bdVal: bdVal), $minVal : min($bdVal))
> accumulate( Fact( $bdVal2: bdVal, $bdVal2 > $minVal), $minVal2 : min($bdVal2))
>
> $minFact: Fact( bdVal == new BigDecimal($minVal.intValue()))
> $minFact2: Fact( bdVal == new BigDecimal($minVal2.intValue()))
> then
> ...
> end
> {noformat}
> But after upgrading to RHPAM 7 and setting drools.propertySpecific=ALLOWED, this does not work.
> i.e. rule fires one more time than expected even though there is only one fact at the last iteration.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4896) Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALWAYS
by Hiroko Miura (Jira)
[ https://issues.redhat.com/browse/DROOLS-4896?page=com.atlassian.jira.plug... ]
Hiroko Miura updated DROOLS-4896:
---------------------------------
Description:
Regarding accumulate, min function with BigDecimal does not work as expected when drools.propertySpecific is "ALLOWED".
The following rule worked with BRMS6.1.4(6.2.0.Final-redhat-13).
{noformat}
rule "rule1_BigDecimal"
agenda-group "BigDecimal"
when
accumulate( Fact( $bdVal: bdVal), $minVal : min($bdVal))
accumulate( Fact( $bdVal2: bdVal, $bdVal2 > $minVal), $minVal2 : min($bdVal2))
$minFact: Fact( bdVal == new BigDecimal($minVal.intValue()))
$minFact2: Fact( bdVal == new BigDecimal($minVal2.intValue()))
then
...
end
{noformat}
But after upgrading to RHPAM 7 and setting drools.propertySpecific=ALWAYS, this does not work.
i.e. rule fires one more time than expected even though there is only one fact at the last iteration.
was:
Regarding accumulate, min function with BigDecimal does not work as expected when drools.propertySpecific is "ALWAYS".
The following rule worked with BRMS6.1.4(6.2.0.Final-redhat-13).
{noformat}
rule "rule1_BigDecimal"
agenda-group "BigDecimal"
when
accumulate( Fact( $bdVal: bdVal), $minVal : min($bdVal))
accumulate( Fact( $bdVal2: bdVal, $bdVal2 > $minVal), $minVal2 : min($bdVal2))
$minFact: Fact( bdVal == new BigDecimal($minVal.intValue()))
$minFact2: Fact( bdVal == new BigDecimal($minVal2.intValue()))
then
...
end
{noformat}
But after upgrading to RHPAM 7 and setting drools.propertySpecific=ALWAYS, this does not work.
i.e. rule fires one more time than expected even though there is only one fact at the last iteration.
> Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALWAYS
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-4896
> URL: https://issues.redhat.com/browse/DROOLS-4896
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.14.0.Final, 7.26.0.Final, 7.31.0.Final
> Reporter: Hiroko Miura
> Assignee: Mario Fusco
> Priority: Major
> Labels: support
> Attachments: bigdecimal-accumulate-test.zip
>
>
> Regarding accumulate, min function with BigDecimal does not work as expected when drools.propertySpecific is "ALLOWED".
> The following rule worked with BRMS6.1.4(6.2.0.Final-redhat-13).
> {noformat}
> rule "rule1_BigDecimal"
> agenda-group "BigDecimal"
> when
> accumulate( Fact( $bdVal: bdVal), $minVal : min($bdVal))
> accumulate( Fact( $bdVal2: bdVal, $bdVal2 > $minVal), $minVal2 : min($bdVal2))
>
> $minFact: Fact( bdVal == new BigDecimal($minVal.intValue()))
> $minFact2: Fact( bdVal == new BigDecimal($minVal2.intValue()))
> then
> ...
> end
> {noformat}
> But after upgrading to RHPAM 7 and setting drools.propertySpecific=ALWAYS, this does not work.
> i.e. rule fires one more time than expected even though there is only one fact at the last iteration.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4896) Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALLOWED
by Hiroko Miura (Jira)
[ https://issues.redhat.com/browse/DROOLS-4896?page=com.atlassian.jira.plug... ]
Hiroko Miura updated DROOLS-4896:
---------------------------------
Summary: Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALLOWED (was: Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALWAYS)
> Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALLOWED
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-4896
> URL: https://issues.redhat.com/browse/DROOLS-4896
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.14.0.Final, 7.26.0.Final, 7.31.0.Final
> Reporter: Hiroko Miura
> Assignee: Mario Fusco
> Priority: Major
> Labels: support
> Attachments: bigdecimal-accumulate-test.zip
>
>
> Regarding accumulate, min function with BigDecimal does not work as expected when drools.propertySpecific is "ALLOWED".
> The following rule worked with BRMS6.1.4(6.2.0.Final-redhat-13).
> {noformat}
> rule "rule1_BigDecimal"
> agenda-group "BigDecimal"
> when
> accumulate( Fact( $bdVal: bdVal), $minVal : min($bdVal))
> accumulate( Fact( $bdVal2: bdVal, $bdVal2 > $minVal), $minVal2 : min($bdVal2))
>
> $minFact: Fact( bdVal == new BigDecimal($minVal.intValue()))
> $minFact2: Fact( bdVal == new BigDecimal($minVal2.intValue()))
> then
> ...
> end
> {noformat}
> But after upgrading to RHPAM 7 and setting drools.propertySpecific=ALWAYS, this does not work.
> i.e. rule fires one more time than expected even though there is only one fact at the last iteration.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-4896) Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALWAYS
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-4896:
------------------------------------
Summary: Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALWAYS
Key: DROOLS-4896
URL: https://issues.redhat.com/browse/DROOLS-4896
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.31.0.Final, 7.26.0.Final, 7.14.0.Final
Reporter: Hiroko Miura
Assignee: Mario Fusco
Attachments: bigdecimal-accumulate-test.zip
Regarding accumulate, min function with BigDecimal does not work as expected when drools.propertySpecific is "ALWAYS".
The following rule worked with BRMS6.1.4(6.2.0.Final-redhat-13).
{noformat}
rule "rule1_BigDecimal"
agenda-group "BigDecimal"
when
accumulate( Fact( $bdVal: bdVal), $minVal : min($bdVal))
accumulate( Fact( $bdVal2: bdVal, $bdVal2 > $minVal), $minVal2 : min($bdVal2))
$minFact: Fact( bdVal == new BigDecimal($minVal.intValue()))
$minFact2: Fact( bdVal == new BigDecimal($minVal2.intValue()))
then
...
end
{noformat}
But after upgrading to RHPAM 7 and setting drools.propertySpecific=ALWAYS, this does not work.
i.e. rule fires one more time than expected even though there is only one fact at the last iteration.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months