[JBoss JIRA] (DROOLS-5668) Latest drools minor versions broke deserialization from earliest 7.x version due to changes made on the serialization/deserialization of node memories
by Sylvain Lemoine (Jira)
[ https://issues.redhat.com/browse/DROOLS-5668?page=com.atlassian.jira.plug... ]
Sylvain Lemoine edited comment on DROOLS-5668 at 9/24/20 4:30 PM:
------------------------------------------------------------------
ok thanks you for considering this issue
was (Author: slem1):
ok thanks you for considering this issue as deserialization of kieSession from previous drools version is pretty critical for our project.
> Latest drools minor versions broke deserialization from earliest 7.x version due to changes made on the serialization/deserialization of node memories
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5668
> URL: https://issues.redhat.com/browse/DROOLS-5668
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.43.1.Final
> Reporter: Sylvain Lemoine
> Assignee: Mario Fusco
> Priority: Major
> Attachments: drools-node-memories-serialization.tar.gz
>
>
> Latest drools minor versions broke deserialization from earliest 7.x version due to changes made on the serialization/deserialization
> of node memories. For instance it happens if a serialization has been done with earliest version and accumulate node.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (DROOLS-5668) Latest drools minor versions broke deserialization from earliest 7.x version due to changes made on the serialization/deserialization of node memories
by Sylvain Lemoine (Jira)
[ https://issues.redhat.com/browse/DROOLS-5668?page=com.atlassian.jira.plug... ]
Sylvain Lemoine edited comment on DROOLS-5668 at 9/24/20 4:29 PM:
------------------------------------------------------------------
ok thanks you for considering this issue as deserialization of kieSession from previous drools version is pretty critical for our project.
was (Author: slem1):
ok thanks you for considering this issue as deserialization of kieSession from previous drools version is pretty critical for our project.
Anyway, I push a bit further my investigations and simply letting pass accumulate node as I did was obviously wrong due to the way tuple for dormant activation are now fully serialized (A), and it takes part in the definition of the activationkey in dormantActivations. As (A) is not present in earliest 7.x serialized session, the following piece of code is not able to filter dormant activation:
{code:java}
RuleImpl rule = activation.getRule();
ActivationKey activationKey = PersisterHelper.hasNodeMemory( rtn ) ?
PersisterHelper.createActivationKey( rule.getPackageName(), rule.getName(), activation.getTuple().toObjects(true)) :
PersisterHelper.createActivationKey( rule.getPackageName(), rule.getName(), activation.getTuple() );
this.tuplesCache.put( activationKey, activation.getTuple() );
return !dormantActivations.contains(activationKey);{code}
> Latest drools minor versions broke deserialization from earliest 7.x version due to changes made on the serialization/deserialization of node memories
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5668
> URL: https://issues.redhat.com/browse/DROOLS-5668
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.43.1.Final
> Reporter: Sylvain Lemoine
> Assignee: Mario Fusco
> Priority: Major
> Attachments: drools-node-memories-serialization.tar.gz
>
>
> Latest drools minor versions broke deserialization from earliest 7.x version due to changes made on the serialization/deserialization
> of node memories. For instance it happens if a serialization has been done with earliest version and accumulate node.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (DROOLS-5668) Latest drools minor versions broke deserialization from earliest 7.x version due to changes made on the serialization/deserialization of node memories
by Sylvain Lemoine (Jira)
[ https://issues.redhat.com/browse/DROOLS-5668?page=com.atlassian.jira.plug... ]
Sylvain Lemoine edited comment on DROOLS-5668 at 9/24/20 4:28 PM:
------------------------------------------------------------------
ok thanks you for considering this issue as deserialization of kieSession from previous drools version is pretty critical for our project.
Anyway, I push a bit further my investigations and simply letting pass accumulate node as I did was obviously wrong due to the way tuple for dormant activation are now fully serialized (A), and it takes part in the definition of the activationkey in dormantActivations. As (A) is not present in earliest 7.x serialized session, the following piece of code is not able to filter dormant activation:
{code:java}
RuleImpl rule = activation.getRule();
ActivationKey activationKey = PersisterHelper.hasNodeMemory( rtn ) ?
PersisterHelper.createActivationKey( rule.getPackageName(), rule.getName(), activation.getTuple().toObjects(true)) :
PersisterHelper.createActivationKey( rule.getPackageName(), rule.getName(), activation.getTuple() );
this.tuplesCache.put( activationKey, activation.getTuple() );
return !dormantActivations.contains(activationKey);{code}
was (Author: slem1):
I push a bit further my investigations, seems due to the way tuple for dormant activation are now fully serialized (A), and it takes part in the definition of the activationkey in dormantActivations. As (A) is not present in earliest 7.x serialized session, the following piece of code is not able to filter dormant activation:
{code:java}
RuleImpl rule = activation.getRule();
ActivationKey activationKey = PersisterHelper.hasNodeMemory( rtn ) ?
PersisterHelper.createActivationKey( rule.getPackageName(), rule.getName(), activation.getTuple().toObjects(true)) :
PersisterHelper.createActivationKey( rule.getPackageName(), rule.getName(), activation.getTuple() );
this.tuplesCache.put( activationKey, activation.getTuple() );
return !dormantActivations.contains(activationKey);{code}
> Latest drools minor versions broke deserialization from earliest 7.x version due to changes made on the serialization/deserialization of node memories
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5668
> URL: https://issues.redhat.com/browse/DROOLS-5668
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.43.1.Final
> Reporter: Sylvain Lemoine
> Assignee: Mario Fusco
> Priority: Major
> Attachments: drools-node-memories-serialization.tar.gz
>
>
> Latest drools minor versions broke deserialization from earliest 7.x version due to changes made on the serialization/deserialization
> of node memories. For instance it happens if a serialization has been done with earliest version and accumulate node.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (DROOLS-5668) Latest drools minor versions broke deserialization from earliest 7.x version due to changes made on the serialization/deserialization of node memories
by Sylvain Lemoine (Jira)
[ https://issues.redhat.com/browse/DROOLS-5668?page=com.atlassian.jira.plug... ]
Sylvain Lemoine commented on DROOLS-5668:
-----------------------------------------
I push a bit further my investigations, seems due to the way tuple for dormant activation are now fully serialized (A), and it takes part in the definition of the activationkey in dormantActivations. As (A) is not present in earliest 7.x serialized session, the following piece of code is not able to filter dormant activation:
{code:java}
RuleImpl rule = activation.getRule();
ActivationKey activationKey = PersisterHelper.hasNodeMemory( rtn ) ?
PersisterHelper.createActivationKey( rule.getPackageName(), rule.getName(), activation.getTuple().toObjects(true)) :
PersisterHelper.createActivationKey( rule.getPackageName(), rule.getName(), activation.getTuple() );
this.tuplesCache.put( activationKey, activation.getTuple() );
return !dormantActivations.contains(activationKey);{code}
> Latest drools minor versions broke deserialization from earliest 7.x version due to changes made on the serialization/deserialization of node memories
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5668
> URL: https://issues.redhat.com/browse/DROOLS-5668
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.43.1.Final
> Reporter: Sylvain Lemoine
> Assignee: Mario Fusco
> Priority: Major
> Attachments: drools-node-memories-serialization.tar.gz
>
>
> Latest drools minor versions broke deserialization from earliest 7.x version due to changes made on the serialization/deserialization
> of node memories. For instance it happens if a serialization has been done with earliest version and accumulate node.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (WFCORE-5134) AuditLogToTLSSyslogTestCase stucks with oracle JDK 11
by Sonia Zaldana (Jira)
[ https://issues.redhat.com/browse/WFCORE-5134?page=com.atlassian.jira.plug... ]
Sonia Zaldana commented on WFCORE-5134:
---------------------------------------
The test case passes with JDK13+ and with JDK 11.0.7. It hangs intermittently with JDK 11.0.8. Given these findings, it seems like the hang is due to a JDK issue and perhaps it may be related to the fix for [https://bugs.openjdk.java.net/browse/JDK-8219991]
[~ropalka], would you happen to have any thoughts on this?
> AuditLogToTLSSyslogTestCase stucks with oracle JDK 11
> -----------------------------------------------------
>
> Key: WFCORE-5134
> URL: https://issues.redhat.com/browse/WFCORE-5134
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Jean Francois Denise
> Priority: Major
>
> I am using oracle JDK 11, the test get stucks in tear down attempting to execute server tearDown action. I noticed that this test is not run on JDK12 due to a deadlock. The observed problem smells deadlock although jstack doesn't report any.
> JDK:
> java 11.0.8 2020-07-14 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.8+10-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.8+10-LTS, mixed mode)
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (WFLY-13897) infinispan-server instances provisioned by testsuite never shutdown
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-13897:
-----------------------------------
Summary: infinispan-server instances provisioned by testsuite never shutdown
Key: WFLY-13897
URL: https://issues.redhat.com/browse/WFLY-13897
Project: WildFly
Issue Type: Bug
Components: Clustering, Test Suite
Affects Versions: 21.0.0.Beta1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Running the clustering testsuite locally leaves 9 instances of infinispan-server running. This wreaks havoc on the CI, which will remain running until the VM shuts down.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (DROOLS-5671) [DMN Designer] Text annotation causes unexpected system error
by Guilherme Gomes (Jira)
[ https://issues.redhat.com/browse/DROOLS-5671?page=com.atlassian.jira.plug... ]
Guilherme Gomes closed DROOLS-5671.
-----------------------------------
Resolution: Duplicate Issue
This JIRA represents the same issue reported on https://issues.redhat.com/browse/DROOLS-5667 and it's addressed by this PR https://github.com/kiegroup/kie-wb-common/pull/3433
> [DMN Designer] Text annotation causes unexpected system error
> -------------------------------------------------------------
>
> Key: DROOLS-5671
> URL: https://issues.redhat.com/browse/DROOLS-5671
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.44.0.Final
> Reporter: Lubomír Terifaj
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> Creating Text annotation causes unexpected system error.
> Error details:
> {code:java}
> Uncaught exception: Exception caught: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.controls.event.BuildCanvasShapeEvent, BeanReference=BuildCanvasShapeEvent [definition=org.kie.workbench.common.dmn.api.definition.model.TextAnnotation@85a8abd2, factory=org.kie.workbench.common.dmn.client.shape.factory.DMNShapeFactory@4941, clientX=674, clientY=350], FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.controls.event.BuildCanvasShapeEvent, BeanReference=BuildCanvasShapeEvent [definition=org.kie.workbench.common.dmn.api.definition.model.TextAnnotation@85a8abd2, factory=org.kie.workbench.common.dmn.client.shape.factory.DMNShapeFactory@4941, clientX=674, clientY=350], FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent@4bb7, FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent@4bb6, FromClient=1 sent to [unavailable] Caused by: (TypeError) : c is null
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (DROOLS-5672) [DMN Designer] Text annotation causes unexpected system error
by Lubomír Terifaj (Jira)
Lubomír Terifaj created DROOLS-5672:
---------------------------------------
Summary: [DMN Designer] Text annotation causes unexpected system error
Key: DROOLS-5672
URL: https://issues.redhat.com/browse/DROOLS-5672
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.44.0.Final
Reporter: Lubomír Terifaj
Assignee: Guilherme Gomes
Creating Text annotation causes unexpected system error.
Error details:
{code:java}
Uncaught exception: Exception caught: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.controls.event.BuildCanvasShapeEvent, BeanReference=BuildCanvasShapeEvent [definition=org.kie.workbench.common.dmn.api.definition.model.TextAnnotation@85a8abd2, factory=org.kie.workbench.common.dmn.client.shape.factory.DMNShapeFactory@4941, clientX=674, clientY=350], FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.controls.event.BuildCanvasShapeEvent, BeanReference=BuildCanvasShapeEvent [definition=org.kie.workbench.common.dmn.api.definition.model.TextAnnotation@85a8abd2, factory=org.kie.workbench.common.dmn.client.shape.factory.DMNShapeFactory@4941, clientX=674, clientY=350], FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent@4bb7, FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent@4bb6, FromClient=1 sent to [unavailable] Caused by: (TypeError) : c is null
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years