[JBoss JIRA] (DROOLS-5422) Fix DMN-PMML integration/managed fields
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5422?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-5422:
-------------------------------------
Description:
>From [Output|[http://dmg.org/pmml/v4-4/Output.html]] documentation:
"If present, the attribute {{targetField}} must refer either to a {{MiningField}} of usage type {{target}} or a field described in {{Targets}} element. {{targetField}} is a required attribute in case the model has multiple target fields."
"predictedValue
Select the raw predicted value. More than one OutputField element can have the predictedValue feature only if the model predicts more than one field. Details can be found in the description of the individual models."
>From [MiningSchema|[http://dmg.org/pmml/v4-4/MiningSchema.html]] documentation:
"*predicted*: field whose value is predicted by the model. As of PMML 4.2, this is deprecated and it has been replaced by the usage type {{target}}."
So, _predicted_ field(s) is/are the one(s) defined as "_target/predicted_" inside _MiningSchema_ or the one(s) defined inside [Targets|[http://dmg.org/pmml/v4-4/Targets.html]] element.
_Output_ has to be considered as _additional_ results; it does not _necessarily_ contains the _target/predicted_ value; *but* the _target/predicted_ value should always be returned.
Currently, DMN (see DMNKiePMMLInvocationEvaluator as example) implement the following algorithm:
1) if "_Output_" element is present, it only manage it (ignores _MiningSchema_ fields)
2) if "_Output_" element is not present, it retrieves "_target_" from _MiningSchema_.
This approach has the following issues
1) it is not mandatory to have the "_target/predicted_" field referenced inside the "_Output_" element; but with the current implementation, the user is "_forced_" to duplicate target reference inside "_Output_" if s/he wants additional outputs from model
2) it completely ignores "_Targets_" element
With this PR, DMN will manage both the _Output_ elements (if present) and all the _target/predicted_ fields, regardless of where/how they are defined.
If such _target/predicted_ fields is/are referred *also* in Output element, only the one(s) inside _Output_ will be managed.
If _Output_ does not define "_target/predicted_" _OutputField_(s), the one(s) from _MiningSchema_ or _Targets_ will be managed.
was:
>From [Output|[http://dmg.org/pmml/v4-4/Output.html]] documentation:
"If present, the attribute {{targetField}} must refer either to a {{MiningField}} of usage type {{target}} or a field described in {{Targets}} element. {{targetField}} is a required attribute in case the model has multiple target fields."
"predictedValue
Select the raw predicted value. More than one OutputField element can have the predictedValue feature only if the model predicts more than one field. Details can be found in the description of the individual models."
>From [MiningSchema|[http://dmg.org/pmml/v4-4/MiningSchema.html]] documentation:
"*predicted*: field whose value is predicted by the model. As of PMML 4.2, this is deprecated and it has been replaced by the usage type {{target}}."
So, _predicted_ field(s) is/are the one(s) defined as "_target/predicted_" inside _MiningSchema_ or the one(s) defined inside [Targets|[http://dmg.org/pmml/v4-4/Targets.html]] element.
_Output_ has to be considered as _additional_ results; it does not _necessarily_ contains the _target/predicted_ value; *but* the _target/predicted_ value should always be returned.
Currently, DMN (see DMNKiePMMLInvocationEvaluator as example) implement the following algorithm:
1) if "_Output_" element is present, it only manage it (ignores _MiningSchema_ fields)
2) if "_Output_" element is not present, it retrieves "_target_" from _MiningSchema_.
This approach has the following issues
1) it is not mandatory to have the "_target/predicted_" field referenced inside the "_Output_" element; but with the current implementation, the user is "_forced_" to duplicate target reference inside "_Output_" if s/he wants additional outputs from model
2) it completely ignores "_Targets_" element
With this PR, DMN will manage both the _Output_ elements (if present) and all the _target/predicted_ fields, regardless of where/how they are defined.
If such _target/predicted_ fields is/are referred *also* in Output element, only the one(s) inside _Output_ will be managed.
If _Output_ does not define "t_arget/predicted_" _OutputField_(s), the one(s) from _MiningSchema_ or _Targets_ will be managed.
> Fix DMN-PMML integration/managed fields
> ---------------------------------------
>
> Key: DROOLS-5422
> URL: https://issues.redhat.com/browse/DROOLS-5422
> Project: Drools
> Issue Type: Task
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
>
> From [Output|[http://dmg.org/pmml/v4-4/Output.html]] documentation:
> "If present, the attribute {{targetField}} must refer either to a {{MiningField}} of usage type {{target}} or a field described in {{Targets}} element. {{targetField}} is a required attribute in case the model has multiple target fields."
> "predictedValue
> Select the raw predicted value. More than one OutputField element can have the predictedValue feature only if the model predicts more than one field. Details can be found in the description of the individual models."
> From [MiningSchema|[http://dmg.org/pmml/v4-4/MiningSchema.html]] documentation:
> "*predicted*: field whose value is predicted by the model. As of PMML 4.2, this is deprecated and it has been replaced by the usage type {{target}}."
>
> So, _predicted_ field(s) is/are the one(s) defined as "_target/predicted_" inside _MiningSchema_ or the one(s) defined inside [Targets|[http://dmg.org/pmml/v4-4/Targets.html]] element.
>
> _Output_ has to be considered as _additional_ results; it does not _necessarily_ contains the _target/predicted_ value; *but* the _target/predicted_ value should always be returned.
>
> Currently, DMN (see DMNKiePMMLInvocationEvaluator as example) implement the following algorithm:
> 1) if "_Output_" element is present, it only manage it (ignores _MiningSchema_ fields)
> 2) if "_Output_" element is not present, it retrieves "_target_" from _MiningSchema_.
> This approach has the following issues
> 1) it is not mandatory to have the "_target/predicted_" field referenced inside the "_Output_" element; but with the current implementation, the user is "_forced_" to duplicate target reference inside "_Output_" if s/he wants additional outputs from model
> 2) it completely ignores "_Targets_" element
> With this PR, DMN will manage both the _Output_ elements (if present) and all the _target/predicted_ fields, regardless of where/how they are defined.
>
> If such _target/predicted_ fields is/are referred *also* in Output element, only the one(s) inside _Output_ will be managed.
> If _Output_ does not define "_target/predicted_" _OutputField_(s), the one(s) from _MiningSchema_ or _Targets_ will be managed.
>
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5422) Fix DMN-PMML integration/managed fields
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5422?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-5422:
-------------------------------------
Description:
>From [Output|[http://dmg.org/pmml/v4-4/Output.html]] documentation:
"If present, the attribute {{targetField}} must refer either to a {{MiningField}} of usage type {{target}} or a field described in {{Targets}} element. {{targetField}} is a required attribute in case the model has multiple target fields."
"predictedValue
Select the raw predicted value. More than one OutputField element can have the predictedValue feature only if the model predicts more than one field. Details can be found in the description of the individual models."
>From [MiningSchema|[http://dmg.org/pmml/v4-4/MiningSchema.html]] documentation:
"*predicted*: field whose value is predicted by the model. As of PMML 4.2, this is deprecated and it has been replaced by the usage type {{target}}."
So, _predicted_ field(s) is/are the one(s) defined as "_target/predicted_" inside _MiningSchema_ or the one(s) defined inside [Targets|[http://dmg.org/pmml/v4-4/Targets.html]] element.
_Output_ has to be considered as _additional_ results; it does not _necessarily_ contains the _target/predicted_ value; *but* the _target/predicted_ value should always be returned.
Currently, DMN (see DMNKiePMMLInvocationEvaluator as example) implement the following algorithm:
1) if "_Output_" element is present, it only manage it (ignores _MiningSchema_ fields)
2) if "_Output_" element is not present, it retrieves "_target_" from _MiningSchema_.
This approach has the following issues
1) it is not mandatory to have the "_target/predicted_" field referenced inside the "_Output_" element; but with the current implementation, the user is "_forced_" to duplicate target reference inside "_Output_" if s/he wants additional outputs from model
2) it completely ignores "_Targets_" element
With this PR, DMN will manage both the _Output_ elements (if present) and all the _target/predicted_ fields, regardless of where/how they are defined.
If such _target/predicted_ fields is/are referred *also* in Output element, only the one(s) inside _Output_ will be managed.
If _Output_ does not define "t_arget/predicted_" _OutputField_(s), the one(s) from _MiningSchema_ or _Targets_ will be managed.
was:
>From [Output|[http://dmg.org/pmml/v4-4/Output.html]] documentation:
"If present, the attribute {{targetField}} must refer either to a {{MiningField}} of usage type {{target}} or a field described in {{Targets}} element. {{targetField}} is a required attribute in case the model has multiple target fields."
"predictedValue
Select the raw predicted value. More than one OutputField element can have the predictedValue feature only if the model predicts more than one field. Details can be found in the description of the individual models."
>From [MiningSchema|[http://dmg.org/pmml/v4-4/MiningSchema.html]] documentation:
"*predicted*: field whose value is predicted by the model. As of PMML 4.2, this is deprecated and it has been replaced by the usage type {{target}}."
So, _predicted_ field(s) is/are the one(s) defined as "_target/predicted_" inside _MiningSchema_ or the one(s) defined inside [Targets|[http://dmg.org/pmml/v4-4/Targets.html]] element.
Output have to be considered as _additional_ results; it does not _necessarily_ contains the _target/predicted_ value; *but* the _target/predicted_ value should always be returned.
Currently, DMN (see DMNKiePMMLInvocationEvaluator as example) implement the following algorithm:
1) if "_Output_" element is present, it only manage it (ignores _MiningSchema_ fields)
2) if "_Output_" element is not present, it retrieves "_target_" from _MiningSchema_.
This approach has the following issues
1) it is not mandatory to have the "_target/predicted_" field referenced inside the "_Output_" element; but with the current implementation, the user is "_forced_" to duplicate target reference inside "_Output_" if s/he wants additional outputs from model
2) it completely ignores "_Targets_" element
With this PR, DMN will manage both the _Output_ elements (if present) and all the _target/predicted_ fields, regardless of where/how they are defined.
If such _target/predicted_ fields is/are referred *also* in Output element, only the one(s) inside _Output_ will be managed.
If _Output_ does not define "t_arget/predicted_" _OutputField_(s), the one(s) from _MiningSchema_ or _Targets_ will be managed.
> Fix DMN-PMML integration/managed fields
> ---------------------------------------
>
> Key: DROOLS-5422
> URL: https://issues.redhat.com/browse/DROOLS-5422
> Project: Drools
> Issue Type: Task
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
>
> From [Output|[http://dmg.org/pmml/v4-4/Output.html]] documentation:
> "If present, the attribute {{targetField}} must refer either to a {{MiningField}} of usage type {{target}} or a field described in {{Targets}} element. {{targetField}} is a required attribute in case the model has multiple target fields."
> "predictedValue
> Select the raw predicted value. More than one OutputField element can have the predictedValue feature only if the model predicts more than one field. Details can be found in the description of the individual models."
> From [MiningSchema|[http://dmg.org/pmml/v4-4/MiningSchema.html]] documentation:
> "*predicted*: field whose value is predicted by the model. As of PMML 4.2, this is deprecated and it has been replaced by the usage type {{target}}."
>
> So, _predicted_ field(s) is/are the one(s) defined as "_target/predicted_" inside _MiningSchema_ or the one(s) defined inside [Targets|[http://dmg.org/pmml/v4-4/Targets.html]] element.
>
> _Output_ has to be considered as _additional_ results; it does not _necessarily_ contains the _target/predicted_ value; *but* the _target/predicted_ value should always be returned.
>
> Currently, DMN (see DMNKiePMMLInvocationEvaluator as example) implement the following algorithm:
> 1) if "_Output_" element is present, it only manage it (ignores _MiningSchema_ fields)
> 2) if "_Output_" element is not present, it retrieves "_target_" from _MiningSchema_.
> This approach has the following issues
> 1) it is not mandatory to have the "_target/predicted_" field referenced inside the "_Output_" element; but with the current implementation, the user is "_forced_" to duplicate target reference inside "_Output_" if s/he wants additional outputs from model
> 2) it completely ignores "_Targets_" element
> With this PR, DMN will manage both the _Output_ elements (if present) and all the _target/predicted_ fields, regardless of where/how they are defined.
>
> If such _target/predicted_ fields is/are referred *also* in Output element, only the one(s) inside _Output_ will be managed.
> If _Output_ does not define "t_arget/predicted_" _OutputField_(s), the one(s) from _MiningSchema_ or _Targets_ will be managed.
>
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5422) Fix DMN-PMML integration/managed fields
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5422?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-5422:
-------------------------------------
Description:
>From [Output|[http://dmg.org/pmml/v4-4/Output.html]] documentation:
"If present, the attribute {{targetField}} must refer either to a {{MiningField}} of usage type {{target}} or a field described in {{Targets}} element. {{targetField}} is a required attribute in case the model has multiple target fields."
"predictedValue
Select the raw predicted value. More than one OutputField element can have the predictedValue feature only if the model predicts more than one field. Details can be found in the description of the individual models."
>From [MiningSchema|[http://dmg.org/pmml/v4-4/MiningSchema.html]] documentation:
"*predicted*: field whose value is predicted by the model. As of PMML 4.2, this is deprecated and it has been replaced by the usage type {{target}}."
So, _predicted_ field(s) is/are the one(s) defined as "_target/predicted_" inside _MiningSchema_ or the one(s) defined inside [Targets|[http://dmg.org/pmml/v4-4/Targets.html]] element.
Output have to be considered as _additional_ results; it does not _necessarily_ contains the _target/predicted_ value; *but* the _target/predicted_ value should always be returned.
Currently, DMN (see DMNKiePMMLInvocationEvaluator as example) implement the following algorithm:
1) if "_Output_" element is present, it only manage it (ignores _MiningSchema_ fields)
2) if "_Output_" element is not present, it retrieves "_target_" from _MiningSchema_.
This approach has the following issues
1) it is not mandatory to have the "_target/predicted_" field referenced inside the "_Output_" element; but with the current implementation, the user is "_forced_" to duplicate target reference inside "_Output_" if s/he wants additional outputs from model
2) it completely ignores "_Targets_" element
With this PR, DMN will manage both the _Output_ elements (if present) and all the _target/predicted_ fields, regardless of where/how they are defined.
If such _target/predicted_ fields is/are referred *also* in Output element, only the one(s) inside _Output_ will be managed.
If _Output_ does not define "t_arget/predicted_" _OutputField_(s), the one(s) from _MiningSchema_ or _Targets_ will be managed.
was:
>From [Output|[http://dmg.org/pmml/v4-4/Output.html]] documentation:
"If present, the attribute {{targetField}} must refer either to a {{MiningField}} of usage type {{target}} or a field described in {{Targets}} element. {{targetField}} is a required attribute in case the model has multiple target fields."
"predictedValue
Select the raw predicted value. More than one OutputField element can have the predictedValue feature only if the model predicts more than one field. Details can be found in the description of the individual models."
>From [MiningSchema|[http://dmg.org/pmml/v4-4/MiningSchema.html]] documentation:
"*predicted*: field whose value is predicted by the model. As of PMML 4.2, this is deprecated and it has been replaced by the usage type {{target}}."
So, predicted field(s) is/are the one(s) defined i"target/predicted" inside _MiningSchema_ or inside [Targets|[http://dmg.org/pmml/v4-4/Targets.html]] element.
Output have to be considered as _additional_ results; it does not _necessarily_ contains the _target/predicted_ value; *but* the _target/predicted_ value should always be returned.
Currently, DMN (see DMNKiePMMLInvocationEvaluator as example) implement the following algorithm:
1) if "_Output_" element is present, it only manage it (ignores _MiningSchema_ fields)
2) if "_Output_" element is not present, it retrieves "_target_" from _MiningSchema_.
This approach has the following issues
1) it is not mandatory to have the "_target/predicted_" field referenced inside the "_Output_" element; but with the current implementation, the user is "_forced_" to duplicate target reference inside "_Output_" if s/he wants additional outputs from model
2) it completely ignores "_Targets_" element
With this PR, DMN will manage both the _Output_ elements (if present) and all the _target/predicted_ fields, regardless of where/how they are defined.
If such _target/predicted_ fields is/are referred *also* in Output element, only the one(s) inside _Output_ will be managed.
If _Output_ does not define "t_arget/predicted_" _OutputField_(s), the one(s) from _MiningSchema_ or _Targets_ will be managed.
> Fix DMN-PMML integration/managed fields
> ---------------------------------------
>
> Key: DROOLS-5422
> URL: https://issues.redhat.com/browse/DROOLS-5422
> Project: Drools
> Issue Type: Task
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
>
> From [Output|[http://dmg.org/pmml/v4-4/Output.html]] documentation:
> "If present, the attribute {{targetField}} must refer either to a {{MiningField}} of usage type {{target}} or a field described in {{Targets}} element. {{targetField}} is a required attribute in case the model has multiple target fields."
> "predictedValue
> Select the raw predicted value. More than one OutputField element can have the predictedValue feature only if the model predicts more than one field. Details can be found in the description of the individual models."
> From [MiningSchema|[http://dmg.org/pmml/v4-4/MiningSchema.html]] documentation:
> "*predicted*: field whose value is predicted by the model. As of PMML 4.2, this is deprecated and it has been replaced by the usage type {{target}}."
>
> So, _predicted_ field(s) is/are the one(s) defined as "_target/predicted_" inside _MiningSchema_ or the one(s) defined inside [Targets|[http://dmg.org/pmml/v4-4/Targets.html]] element.
>
> Output have to be considered as _additional_ results; it does not _necessarily_ contains the _target/predicted_ value; *but* the _target/predicted_ value should always be returned.
>
> Currently, DMN (see DMNKiePMMLInvocationEvaluator as example) implement the following algorithm:
> 1) if "_Output_" element is present, it only manage it (ignores _MiningSchema_ fields)
> 2) if "_Output_" element is not present, it retrieves "_target_" from _MiningSchema_.
> This approach has the following issues
> 1) it is not mandatory to have the "_target/predicted_" field referenced inside the "_Output_" element; but with the current implementation, the user is "_forced_" to duplicate target reference inside "_Output_" if s/he wants additional outputs from model
> 2) it completely ignores "_Targets_" element
> With this PR, DMN will manage both the _Output_ elements (if present) and all the _target/predicted_ fields, regardless of where/how they are defined.
>
> If such _target/predicted_ fields is/are referred *also* in Output element, only the one(s) inside _Output_ will be managed.
> If _Output_ does not define "t_arget/predicted_" _OutputField_(s), the one(s) from _MiningSchema_ or _Targets_ will be managed.
>
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5422) Fix DMN-PMML integration/managed fields
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-5422:
----------------------------------------
Summary: Fix DMN-PMML integration/managed fields
Key: DROOLS-5422
URL: https://issues.redhat.com/browse/DROOLS-5422
Project: Drools
Issue Type: Task
Reporter: Gabriele Cardosi
Assignee: Gabriele Cardosi
>From [Output|[http://dmg.org/pmml/v4-4/Output.html]] documentation:
"If present, the attribute {{targetField}} must refer either to a {{MiningField}} of usage type {{target}} or a field described in {{Targets}} element. {{targetField}} is a required attribute in case the model has multiple target fields."
"predictedValue
Select the raw predicted value. More than one OutputField element can have the predictedValue feature only if the model predicts more than one field. Details can be found in the description of the individual models."
>From [MiningSchema|[http://dmg.org/pmml/v4-4/MiningSchema.html]] documentation:
"*predicted*: field whose value is predicted by the model. As of PMML 4.2, this is deprecated and it has been replaced by the usage type {{target}}."
So, predicted field(s) is/are the one(s) defined i"target/predicted" inside _MiningSchema_ or inside [Targets|[http://dmg.org/pmml/v4-4/Targets.html]] element.
Output have to be considered as _additional_ results; it does not _necessarily_ contains the _target/predicted_ value; *but* the _target/predicted_ value should always be returned.
Currently, DMN (see DMNKiePMMLInvocationEvaluator as example) implement the following algorithm:
1) if "_Output_" element is present, it only manage it (ignores _MiningSchema_ fields)
2) if "_Output_" element is not present, it retrieves "_target_" from _MiningSchema_.
This approach has the following issues
1) it is not mandatory to have the "_target/predicted_" field referenced inside the "_Output_" element; but with the current implementation, the user is "_forced_" to duplicate target reference inside "_Output_" if s/he wants additional outputs from model
2) it completely ignores "_Targets_" element
With this PR, DMN will manage both the _Output_ elements (if present) and all the _target/predicted_ fields, regardless of where/how they are defined.
If such _target/predicted_ fields is/are referred *also* in Output element, only the one(s) inside _Output_ will be managed.
If _Output_ does not define "t_arget/predicted_" _OutputField_(s), the one(s) from _MiningSchema_ or _Targets_ will be managed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5321) Failing test org.kie.hacep.LocalStorageKieSessionTest.fireUntilHaltTest on timeout
by Marek Novotny (Jira)
[ https://issues.redhat.com/browse/DROOLS-5321?page=com.atlassian.jira.plug... ]
Marek Novotny updated DROOLS-5321:
----------------------------------
Git Pull Request: https://github.com/kiegroup/droolsjbpm-integration/pull/2087, https://github.com/kiegroup/droolsjbpm-integration/pull/2120 (was: https://github.com/kiegroup/droolsjbpm-integration/pull/2087)
> Failing test org.kie.hacep.LocalStorageKieSessionTest.fireUntilHaltTest on timeout
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-5321
> URL: https://issues.redhat.com/browse/DROOLS-5321
> Project: Drools
> Issue Type: Task
> Reporter: Marek Novotny
> Assignee: Massimiliano Dessi
> Priority: Critical
>
> {noformat}
> Error Message
> test timed out after 10000 milliseconds
> Stacktrace
> org.junit.runners.model.TestTimedOutException: test timed out after 10000 milliseconds
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at java.util.concurrent.CompletableFuture$Signaller.block(CompletableFuture.java:1693)
> at java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3323)
> at java.util.concurrent.CompletableFuture.waitingGet(CompletableFuture.java:1729)
> at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)
> at org.kie.hacep.LocalStorageKieSessionTest.fireUntilHaltTest(LocalStorageKieSessionTest.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.lang.Thread.run(Thread.java:748)
> Standard Output
> 17:37:38.475 [main] WARN o.d.c.k.b.impl.ClasspathKieProject getPomPropertiesFromFileSystem - Unable to find pom.properties in /home/jenkins/workspace/KIE/master/upstream-downstream/droolsjbpm-build-bootstrap.downstream/kiegroup_droolsjbpm-integration/drools-ha/ha-core-infra/target/test-classes
> 17:37:39.088 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process Remote command on process:Fact count of 9d177e58-24e5-4b1f-800c-0d0516856f4a from entry-point DEFAULT state:LEADER
> 17:37:39.089 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process sideEffects:[]
> 17:37:39.089 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process new ControlMessage sent to control topic:ControlMessage{offset=0, sideEffects=[], id='9d177e58-24e5-4b1f-800c-0d0516856f4a', timestamp=0}
> 17:37:39.089 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - sideEffectOnLeader:[]
> 17:37:39.091 [Thread-10] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process Remote command on process:Fire until halt of 2a5a4fd4-991d-41ac-99b0-ed7030d8533d state:LEADER
> 17:37:39.091 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process Remote command on process:Insert of RemoteFactHandleImpl{id='0597e023-e5d6-4fdb-9396-04705d3b3353', object=StockTickEvent{company='RHT', price=9.0', timestamp=1589233059090}} into entry-point DEFAULT state:LEADER
> 17:37:39.091 [Thread-10] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process sideEffects:[]
> 17:37:39.091 [Thread-10] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process new ControlMessage sent to control topic:ControlMessage{offset=0, sideEffects=[], id='2a5a4fd4-991d-41ac-99b0-ed7030d8533d', timestamp=0}
> 17:37:39.091 [Thread-10] WARN org.kie.hacep.util.PrinterUtil process - sideEffectOnLeader:[]
> 17:37:39.091 [Thread-10] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process Remote command on process:GetObjectCommand{ remoteFactHandle=RemoteFactHandleImpl{id='0597e023-e5d6-4fdb-9396-04705d3b3353', object=StockTickEvent{company='RHT', price=9.0', timestamp=1589233059090}}} state:LEADER
> 17:37:39.098 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process sideEffects:[]
> 17:37:39.098 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process new ControlMessage sent to control topic:ControlMessage{offset=0, sideEffects=[], id='1a40df01-43a3-4c25-966f-69c5f4233453', timestamp=0}
> 17:37:39.098 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - sideEffectOnLeader:[]
> 17:37:42.600 [pool-12-thread-1] WARN o.k.h.c.i.e.LeaderElectionImpl lookupNewLeaderInfo - Pod[rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com] Unable to retrieve the current ConfigMap default-leaders from Kubernetes
> 17:37:42.939 [pool-15-thread-1] WARN o.k.h.c.i.e.LeaderElectionImpl lookupNewLeaderInfo - Pod[rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com] Unable to retrieve the current ConfigMap default-leaders from Kubernetes
> 17:37:48.299 [pool-15-thread-1] WARN o.k.h.c.i.e.LeaderElectionImpl lookupNewLeaderInfo - Pod[rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com] Unable to retrieve the current ConfigMap default-leaders from Kubernetes
> 17:37:48.332 [pool-12-thread-1] WARN o.k.h.c.i.e.LeaderElectionImpl lookupNewLeaderInfo - Pod[rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com] Unable to retrieve the current ConfigMap default-leaders from Kubernetes
> Standard Error
> Exception in thread "Thread-10" java.lang.IllegalStateException
> at org.kie.hacep.consumer.DroolsConsumerHandler.processCommand(DroolsConsumerHandler.java:182)
> at org.kie.hacep.consumer.DroolsConsumerHandler.process(DroolsConsumerHandler.java:130)
> at org.kie.hacep.core.infra.consumer.LocalConsumer.poll(LocalConsumer.java:50)
> at org.kie.hacep.core.infra.consumer.ConsumerThread.run(ConsumerThread.java:27)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month