[JBoss JIRA] (DROOLS-3460) KIE Server REST Command GetObjects with ObjectFilter not working
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-3460?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-3460:
--------------------------------
Sprint: 2019 Week 41-43 (from Okt 7)
> KIE Server REST Command GetObjects with ObjectFilter not working
> ----------------------------------------------------------------
>
> Key: DROOLS-3460
> URL: https://issues.jboss.org/browse/DROOLS-3460
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 7.15.0.Final
> Environment: RHEL 7.5, EAP 7.1.0, Drools 7.15.0.Final
> Reporter: Balakrishnan Balasubramanian
> Assignee: Mario Fusco
> Priority: Major
>
> Filtering the facts in the GetObjectsCommand doesn't do any object filtering!.
> Here are the two code pieces that were used to set the ObjectFilter into GetObjectsCommand, but didn't produce the expected filtered results.
> *+Trial 1:+*
> {code:java}
> ObjectFilter filter = new ObjectFilter() {
> @Override
> public boolean accept(Object object) {
> return object.getClass().getName().equals("a.b.c.PotentialFraudFact");
> }
> };
> Command<?> getObjects = commandsFactory.newGetObjects(filter, "out");
> {code}
> *+Trial 2:+*
>
> {code:java}
> ClassObjectSerializationFilter filter = new ClassObjectSerializationFilter(PotentialFraudFact.class);
> Command<?> getObjects = commandsFactory.newGetObjects(filter, "out");
> {code}
> In the response, the "out" identifier has *all* facts, not just the ones matching the given filter. It's as if it ignores the filter. Also, no error messages appear in the console.
> When a ClassObjectFilter is used instead of the aforementioned implementations, a ClassNotFoundException (_shown below_) for the a.b.c.PotentialFraudFact.class occurs. This is incorrect as the deployed container/KJAR has this class!.
>
> {code:java}
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.ClassNotFoundException: a.b.c.PotentialFraudFact from [Module "deployment.kie-server.war" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.drools.core.ClassObjectSerializationFilter.accept(ClassObjectSerializationFilter.java:50)
> ... 73 more
> {code}
> The issue is with this line https://github.com/kiegroup/drools/blob/4c6856223b8be47b4fc52c35423be8b50... where the class loader used to find the class couldn't find the class that corresponds to the given Fact.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 4 months
[JBoss JIRA] (DROOLS-4585) Focus doesn't moves after the selected cell
by Anna Dupliak (Jira)
[ https://issues.jboss.org/browse/DROOLS-4585?page=com.atlassian.jira.plugi... ]
Anna Dupliak updated DROOLS-4585:
---------------------------------
Description:
{color:red}*Failure*{color}
If you navigate cell that is obscured by the right panel in header then it dosen't automatically scrolls to it as it done for grid body.
*Expected*
Viewed part of grid follows the selected cell
was:
{color:red}*Failure*{color}
If you navigate cell that is obscured by the right panel in header then it dosen't automatically scrolls to it as it done for grid body.
*{color:red}Expected{color}*
Viewed part of grid follows the selected cell
> Focus doesn't moves after the selected cell
> -------------------------------------------
>
> Key: DROOLS-4585
> URL: https://issues.jboss.org/browse/DROOLS-4585
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: CustomerFocus
>
> {color:red}*Failure*{color}
> If you navigate cell that is obscured by the right panel in header then it dosen't automatically scrolls to it as it done for grid body.
> *Expected*
> Viewed part of grid follows the selected cell
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 4 months
[JBoss JIRA] (DROOLS-4585) Focus doesn't moves after the selected cell
by Anna Dupliak (Jira)
[ https://issues.jboss.org/browse/DROOLS-4585?page=com.atlassian.jira.plugi... ]
Anna Dupliak updated DROOLS-4585:
---------------------------------
Steps to Reproduce:
# Open *Test Scenario Designer*
# Fill up the grid by right click clicking on property header and choose *Insert Colomn Left*
# Repeat step 3 10 times to activate the ability of horizontal scrolling
# Navigate to the *header* cell by arrows keys
# Bring the highlighted cell to the edge of the viewed window and move it further
was:
# Open Test Scenario Designer
# Fill up the grid by right click clicking on property header and choose Insert Colomn Left
# Repeat step 3 10 times to activate the ability of horizontal scrolling
# Navigate to the header cell by arrows keys
# Bring the highlighted cell to the edge of the viewed window and move it further
> Focus doesn't moves after the selected cell
> -------------------------------------------
>
> Key: DROOLS-4585
> URL: https://issues.jboss.org/browse/DROOLS-4585
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: CustomerFocus
>
> {color:red}*Failure*{color}
> If you navigate cell that is obscured by the right panel in header then it dosen't automatically scrolls to it as it done for grid body.
> *{color:red}Expected{color}*
> Viewed part of grid follows the selected cell
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 4 months
[JBoss JIRA] (DROOLS-4585) Focus doesn't moves after the selected cell
by Anna Dupliak (Jira)
Anna Dupliak created DROOLS-4585:
------------------------------------
Summary: Focus doesn't moves after the selected cell
Key: DROOLS-4585
URL: https://issues.jboss.org/browse/DROOLS-4585
Project: Drools
Issue Type: Bug
Components: Scenario Simulation and Testing
Reporter: Anna Dupliak
Assignee: Yeser Amer
{color:red}*Failure*{color}
If you navigate cell that is obscured by the right panel in header then it dosen't automatically scrolls to it as it done for grid body.
*{color:red}Expected{color}*
Viewed part of grid follows the selected cell
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 4 months
[JBoss JIRA] (WFWIP-147) @JMSConnectionFactoryDefinition with property resourceAdapater to pooled-connection-factory defined in messaging-active subsystem does not work
by Emmanuel Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFWIP-147?page=com.atlassian.jira.plugin.... ]
Emmanuel Hugonnet resolved WFWIP-147.
-------------------------------------
Resolution: Done
> @JMSConnectionFactoryDefinition with property resourceAdapater to pooled-connection-factory defined in messaging-active subsystem does not work
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-147
> URL: https://issues.jboss.org/browse/WFWIP-147
> Project: WildFly WIP
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Emmanuel Hugonnet
> Priority: Blocker
>
> If pooled-connection-factory is defined in messaging-active subsystem like:
> {code}
> <http-connector name="connector" socket-binding="messaging-socket-binding" endpoint="acceptor" server-name="default"/>
> <pooled-connection-factory name="activemq-ra-remote" entries="java:/testJmsXA " connectors="connector" transaction="xa"/>
> {code}
> and deployment tries to use it to create @JMSConnectionFactoryDefinition like:
> {code}
> @JMSConnectionFactoryDefinition(
> name="java:/jms/myRemoteJmsCf",
> resourceAdapter="activemq-ra-remote")
> {code}
> then deploy fails with:
> {code}
> 13:21:18,284 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "mdb-activemq-1.0-SNAPSHOT.jar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.raactivator.\"mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf\"" => "WFLYJCA0046: Failed to start RA deployment [mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf]
> Caused by: org.jboss.jca.deployers.common.DeployException: IJ020051: Unable to start org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter
> Caused by: java.lang.IllegalArgumentException: must provide either TransportType or DiscoveryGroupAddress and DiscoveryGroupPort for ResourceAdapter Connection Factory"}}
> 13:21:18,295 INFO [org.jboss.as.server] (ServerService Thread Pool -- 48) WFLYSRV0010: Deployed "mdb-activemq-1.0-SNAPSHOT.jar" (runtime-name : "mdb-activemq-1.0-SNAPSHOT.jar")
> 13:21:18,297 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.connection-factory.reference-factory.jboss.naming.context.java.jms.myRemoteJmsCf (missing) dependents: [service jboss.naming.context.java.jms.myRemoteJmsCf]
> WFLYCTL0186: Services which failed to start: service jboss.raactivator."mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf": WFLYJCA0046: Failed to start RA deployment [mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf]
> WFLYCTL0448: 5 additional services are down due to their dependencies being missing or failed
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 4 months
[JBoss JIRA] (DROOLS-4580) ClassCastException at BuildUtils.mergeNodes with two rules having identical constraints
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-4580?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-4580:
--------------------------------
Sprint: 2019 Week 38-40 (from Sep 16)
> ClassCastException at BuildUtils.mergeNodes with two rules having identical constraints
> ---------------------------------------------------------------------------------------
>
> Key: DROOLS-4580
> URL: https://issues.jboss.org/browse/DROOLS-4580
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.27.0.Final
> Reporter: Martin Weiler
> Assignee: Mario Fusco
> Priority: Major
>
> Building a rule base where two rules have identical constraints fails with a ClassCastException:
> {noformat}
> java.lang.ClassCastException: org.drools.core.rule.constraint.EvaluatorConstraint cannot be cast to org.drools.core.rule.constraint.MvelConstraint
> at org.drools.core.reteoo.builder.BuildUtils.mergeNodes(BuildUtils.java:176)
> at org.drools.core.reteoo.builder.BuildUtils.attachNode(BuildUtils.java:152)
> at org.drools.core.reteoo.builder.GroupElementBuilder$AndBuilder.buildJoinNode(GroupElementBuilder.java:143)
> at org.drools.core.reteoo.builder.GroupElementBuilder$AndBuilder.build(GroupElementBuilder.java:110)
> at org.drools.core.reteoo.builder.GroupElementBuilder.build(GroupElementBuilder.java:68)
> at org.drools.core.reteoo.builder.ReteooRuleBuilder.addSubRule(ReteooRuleBuilder.java:167)
> at org.drools.core.reteoo.builder.ReteooRuleBuilder.addRule(ReteooRuleBuilder.java:139)
> at org.drools.core.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:110)
> at org.drools.core.impl.KnowledgeBaseImpl.internalAddRule(KnowledgeBaseImpl.java:1523)
> at org.drools.core.impl.KnowledgeBaseImpl.internalAddPackages(KnowledgeBaseImpl.java:913)
> at org.drools.core.impl.KnowledgeBaseImpl.lambda$addPackages$2(KnowledgeBaseImpl.java:715)
> at org.drools.core.impl.KnowledgeBaseImpl.enqueueModification(KnowledgeBaseImpl.java:732)
> at org.drools.core.impl.KnowledgeBaseImpl.addPackages(KnowledgeBaseImpl.java:715)
> at org.drools.compiler.kie.builder.impl.AbstractKieModule.createKieBase(AbstractKieModule.java:215)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:406)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieBase(KieContainerImpl.java:396)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieBase(KieContainerImpl.java:391)
> at org.kie.internal.utils.KieHelper.build(KieHelper.java:80)
> at org.drools.compiler.integrationtests.ExpirationTest.testEventSameContraint(ExpirationTest.java:595)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 4 months
[JBoss JIRA] (DROOLS-4584) Scrolling during editing mode move cell in new position on the screen
by Anna Dupliak (Jira)
Anna Dupliak created DROOLS-4584:
------------------------------------
Summary: Scrolling during editing mode move cell in new position on the screen
Key: DROOLS-4584
URL: https://issues.jboss.org/browse/DROOLS-4584
Project: Drools
Issue Type: Bug
Components: Scenario Simulation and Testing
Affects Versions: 7.28.0.Final
Reporter: Anna Dupliak
Assignee: Yeser Amer
Attachments: image-2019-10-01-11-24-36-774.png
!image-2019-10-01-11-24-36-774.png|thumbnail!
Cell moves unexpectedly in editing mode
{color:red}*Failure*{color}
If you start edit any cell of a big grid and then scroll the input would move not in the right cell.
*Expected*
Input element moves with entire table
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 4 months
[JBoss JIRA] (WFWIP-207) UX: Force removal of Operator upon delete - do not hang due to finalizers
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/WFWIP-207?page=com.atlassian.jira.plugin.... ]
Martin Choma closed WFWIP-207.
------------------------------
Verified in brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-operator:jb-eap-7.3-operator-rhel8-containers-candidate-33923-20190926082049
> UX: Force removal of Operator upon delete - do not hang due to finalizers
> -------------------------------------------------------------------------
>
> Key: WFWIP-207
> URL: https://issues.jboss.org/browse/WFWIP-207
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Petr Kremensky
> Assignee: Ondrej Chaloupka
> Priority: Blocker
> Labels: operator
>
> We run yet into another use case where finalizers prevent users from deleting the project - the delete operation hangs.
> pods:
> {noformat}
> $ oc get all
> NAME READY STATUS RESTARTS AGE
> pod/simple-jaxrs-operator-0 0/1 ImagePullBackOff 0 9m11s
> pod/simple-jaxrs-operator-1 0/1 ImagePullBackOff 0 9m11s
> pod/wildfly-operator-686846d6fb-db9sj 1/1 Running
> $ oc delete wildflyserver simple-jaxrs-operator
> wildflyserver.wildfly.org "simple-jaxrs-operator" deleted
> ... hangs forever
> {noformat}
> operator log:
> {noformat}
> {"level":"info","ts":1569308322.2926116,"logger":"controller_wildflyserver","msg":"Reconciling WildFlyServer","Request.Namespace":"pkremens-namespace","Request.Name":"simple-jaxrs-operator"}
> {"level":"info","ts":1569308322.2927597,"logger":"controller_wildflyserver","msg":"WildflyServer is marked for deletion. Waiting for finalizers to clean the workspace","Request.Namespace":"pkremens-namespace","Request.Name":"simple-jaxrs-operator"}
> {"level":"info","ts":1569308322.2929516,"logger":"controller_wildflyserver","msg":"Transaction recovery scaledown processing","Request.Namespace":"pkremens-namespace","Request.Name":"simple-jaxrs-operator","Pod Name":"simple-jaxrs-operator-0","IP Address":"10.128.0.227","Pod State":"SCALING_DOWN_RECOVERY_INVESTIGATION","Pod Phase":"Pending"}
> {"level":"info","ts":1569308322.2931426,"logger":"controller_wildflyserver","msg":"Transaction recovery scaledown processing","Request.Namespace":"pkremens-namespace","Request.Name":"simple-jaxrs-operator","Pod Name":"simple-jaxrs-operator-1","IP Address":"10.128.0.226","Pod State":"SCALING_DOWN_RECOVERY_INVESTIGATION","Pod Phase":"Pending"}
> {"level":"error","ts":1569308322.294659,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"pkremens-namespace/simple-jaxrs-operator","error":"Finalizer processing: failed transaction recovery for WildflyServer pkremens-namespace:simple-jaxrs-operator name Error: Found 2 errors:\n [[Pod 'simple-jaxrs-operator-0' / 'simple-jaxrs-operator' is in pending phase Pending. It will be hopefully started in a while. Transaction recovery needs the pod being fully started to be capable to mark it as clean for the scale down.]], [[Pod 'simple-jaxrs-operator-1' / 'simple-jaxrs-operator' is in pending phase Pending. It will be hopefully started in a while. Transaction recovery needs the pod being fully started to be capable to mark it as clean for the scale down.]],","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {noformat}
> This is a call between safety vs. usability, but we believe that these issues (hanging delete command due to EAP7-1192) could be a serious usability problem for users.
> *actual*
> * scale down can require manual user interaction forced by finalizers
> * delete can hang, requiring manual user interaction (delete deployment object, remove finalizer from operator CR, run delete again)
> *expected*
> * scale down can require manual user interaction forced by finalizers
> * delete should never hang, it should be treated like a pulling a plug (rm -rf), in case users needs to make s graceful shutdown, he make a proper scale down to 0 prior the project deletion - this should be properly documented
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 4 months