[JBoss JIRA] (WFLY-13627) Distributed sessions/SFSBs stored in non-transactional invalidation-cache should schedule expirations locally
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13627?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFLY-13627:
--------------------------------
Description:
Currently, distributed web sessions (and SFSBs) are expired on the primary owner of the session. For non-transactional invalidation caches expiration should always be scheduled locally. This used to be the case, however, the logic for determining this has changed such that expirations happen on the owner of segment 0.
This has the consequence of an RPC cost per request (and one after).
was:Currently, distributed web sessions (and SFSBs) are expired on the primary owner of the session. For non-transactional invalidation caches expiration should always be scheduled locally. This used to be the case, however, the logic for determining this has changed such that expirations happen on the owner of segment 0.
> Distributed sessions/SFSBs stored in non-transactional invalidation-cache should schedule expirations locally
> -------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13627
> URL: https://issues.redhat.com/browse/WFLY-13627
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 20.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Critical
>
> Currently, distributed web sessions (and SFSBs) are expired on the primary owner of the session. For non-transactional invalidation caches expiration should always be scheduled locally. This used to be the case, however, the logic for determining this has changed such that expirations happen on the owner of segment 0.
> This has the consequence of an RPC cost per request (and one after).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (DROOLS-5458) Running tests should not affect incremental build
by Jan Stastny (Jira)
[ https://issues.redhat.com/browse/DROOLS-5458?page=com.atlassian.jira.plug... ]
Jan Stastny commented on DROOLS-5458:
-------------------------------------
Checked that the issue happens also when Data Objects are provided in a separate JAR through Artifact Repository.
> Running tests should not affect incremental build
> -------------------------------------------------
>
> Key: DROOLS-5458
> URL: https://issues.redhat.com/browse/DROOLS-5458
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.39.0.Final
> Reporter: Jan Stastny
> Assignee: Toni Rikkola
> Priority: Blocker
> Labels: drools-tools
> Attachments: bpms_scesim-tickets.zip
>
>
> For a Scenario Simulation that tests DRL rule and facts having an enum property a seemingly class-loading issue occurs in Business Central.
> The ultimate error is in the DRL file validation:
> {code:java|title=DRL file}
> package org.jboss.qa.ba.scesim;
> rule "child ticket"
> when
> t: Ticket ( type==TicketType.CHILD)
> then
> t.setPrice(5.0);
> end
> {code}
> {code:java|title=Validation error}
> [KBase: defaultKieBase]: Unable to Analyse Expression type == TicketType.CHILD:
> [Error: Comparison operation requires compatible types. Found class org.jboss.qa.ba.scesim.TicketType and class org.jboss.qa.ba.scesim.TicketType]
> [Near : {... type == TicketType.CHILD ....}]
> ^
> {code}
> The issue happens in given scenario:
> # import project
> # go to DRL file and run validation - succeeds
> # go to scenario simulation and run - succeeds
> # go back to DRL file and run validation - fails with the error above
> # go to scenario simulation and run again - fails due to the rule not being evaluated for given facts
> The issue disappears when running Build of the project in the Project perspective.
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months