[JBoss JIRA] (WFCORE-4852) ControlledProcessState.State should expose whether a state means a running server
by Yeray Borges Santana (Jira)
Yeray Borges Santana created WFCORE-4852:
--------------------------------------------
Summary: ControlledProcessState.State should expose whether a state means a running server
Key: WFCORE-4852
URL: https://issues.redhat.com/browse/WFCORE-4852
Project: WildFly Core
Issue Type: Enhancement
Components: Management
Reporter: Yeray Borges Santana
Assignee: Brian Stansberry
Fix For: 11.0.0.Beta1
Three of the ControlledProcessState.State enum values indicate the server is actually running, just with different relationships between the running configuration vs the persistent one. Add a boolean getter to distinguish those three from the others that indicate starting, stopping, stopped.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFCORE-4851) Expose CoreProcessStateService functionality used by subsystems via a capability
by Yeray Borges Santana (Jira)
Yeray Borges Santana created WFCORE-4851:
--------------------------------------------
Summary: Expose CoreProcessStateService functionality used by subsystems via a capability
Key: WFCORE-4851
URL: https://issues.redhat.com/browse/WFCORE-4851
Project: WildFly Core
Issue Type: Enhancement
Components: Management
Reporter: Yeray Borges Santana
Assignee: Brian Stansberry
Fix For: 11.0.0.Beta1
Subsystems are injecting CoreProcessStateService to track the process state, and perhaps more should as some are using graceful startup as a kind of trigger for beginning work, when the process reaching RUNNING state would be more appropriate. But:
1) they aren't using a capability for this wiring, because the kernel doesn't expose one
2) ControlledProcessStateService is not a clean API, as it exposes the MSC Service interface which should not be accessible to subsystems.
So, add a ProcessStateNotifier interface, and expose it via a capability. Impl is still ControlledProcessStateService.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5028) Support incremental update for function with executable model
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5028?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5028:
---------------------------------
Sprint: (was: 2020 Week 07-09 (from Feb 10))
> Support incremental update for function with executable model
> -------------------------------------------------------------
>
> Key: DROOLS-5028
> URL: https://issues.redhat.com/browse/DROOLS-5028
> Project: Drools
> Issue Type: Task
> Components: executable model
> Affects Versions: 7.32.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Luca Molteni
> Priority: Major
> Labels: good-first-issue
>
> When you do incremental compilation with executable model, if a function is updated, you will get this error.
> {noformat}
> [ERROR] testKJarUpgradeWithChangedFunction[PATTERN_DSL](org.drools.modelcompiler.IncrementalCompilationTest) Time elapsed: 2.682 s <<< ERROR!
> java.lang.IllegalArgumentException: Unsupported change type: function!
> at org.drools.modelcompiler.builder.CanonicalKieBaseUpdater.run(CanonicalKieBaseUpdater.java:148)
> at org.drools.core.impl.KnowledgeBaseImpl.enqueueModification(KnowledgeBaseImpl.java:745)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.update(KieContainerImpl.java:266)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.update(KieContainerImpl.java:236)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.updateToVersion(KieContainerImpl.java:194)
> at org.drools.modelcompiler.IncrementalCompilationTest.testKJarUpgradeWithChangedFunction(IncrementalCompilationTest.java:359)
> ...
> {noformat}
> This is an explicit limitation at the moment but I filed this JIRA to support a function update.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5050) Issue with alpha node and expired events rule execution
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5050?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5050:
---------------------------------
Story Points: 8
> Issue with alpha node and expired events rule execution
> -------------------------------------------------------
>
> Key: DROOLS-5050
> URL: https://issues.redhat.com/browse/DROOLS-5050
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.33.0.Final
> Reporter: Marcell Pessanha Cruz
> Assignee: Luca Molteni
> Priority: Critical
>
> Alpha node based rules evaluated for expired events are not all executed during the inference cycle.
> With the following rules:
> {noformat}
> declare DummyEvent
> @role( event )
> @timestamp( eventTimestamp )
> @expires( 1s )
> end
> rule R1
> when
> $evt : DummyEvent()
> then
> end
> rule R2
> when
> $evt : ApplicationEvent()
> then
> end
> {noformat}
> and this code to execute:
> {noformat}
> public interface ApplicationEvent { }
> public static class DummyEvent implements ApplicationEvent {...}
> /* .... */
> final KieSession kieSession = kieBase.newKieSession( sessionConfig, null );
> PseudoClockScheduler clock = kieSession.getSessionClock();
> final long currentTime = clock.getCurrentTime();
> clock.advanceTime(10, TimeUnit.SECONDS);
> kieSession.insert(new DummyEvent(10, currentTime));
> kieSession.fireAllRules()
> {noformat}
> then only the *R1* rule is executed, not R2.
> Note: the same test case passes on 7.2.0.Final and earlier versions.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months