[Red Hat JIRA] (DROOLS-5984) DMN Alpha Network - Range Indexing
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5984?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5984:
---------------------------------
Description:
Currently alpha range index is not enabled probably because AlphaNetworkCreation.createAlphaNode() doesn't set an index to a constraint for "Application Risk Score" in DMNDecisionTableAlphaSupportingTest (= ConstraintType is UNKNOWN so CompositeObjectSinkAdapter.isRangeIndexable() returns false.
Also we would need to change range index threshold to test easier).
was:Currently alpha range index is not enabled probably because AlphaNetworkCreation.createAlphaNode() doesn't set an index to a constraint for "Application Risk Score" in DMNDecisionTableAlphaSupportingTest (= ConstraintType is UNKNOWN so CompositeObjectSinkAdapter.isRangeIndexable() returns false. Also we would need to change range index threshold to test easier). We will be able to enhance it in another JIRA?
> DMN Alpha Network - Range Indexing
> ----------------------------------
>
> Key: DROOLS-5984
> URL: https://issues.redhat.com/browse/DROOLS-5984
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
>
> Currently alpha range index is not enabled probably because AlphaNetworkCreation.createAlphaNode() doesn't set an index to a constraint for "Application Risk Score" in DMNDecisionTableAlphaSupportingTest (= ConstraintType is UNKNOWN so CompositeObjectSinkAdapter.isRangeIndexable() returns false.
> Also we would need to change range index threshold to test easier).
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 3 months
[Red Hat JIRA] (DROOLS-5984) DMN Alpha Network - Range Indexing
by Luca Molteni (Jira)
Luca Molteni created DROOLS-5984:
------------------------------------
Summary: DMN Alpha Network - Range Indexing
Key: DROOLS-5984
URL: https://issues.redhat.com/browse/DROOLS-5984
Project: Drools
Issue Type: Bug
Components: dmn engine
Reporter: Luca Molteni
Assignee: Luca Molteni
Verify that indexes are generated correctly.
This should also give some performance different, try measure it with a benchmark.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 3 months
[Red Hat JIRA] (DROOLS-5983) DMN Alpha Network - Verify Indexing
by Luca Molteni (Jira)
Luca Molteni created DROOLS-5983:
------------------------------------
Summary: DMN Alpha Network - Verify Indexing
Key: DROOLS-5983
URL: https://issues.redhat.com/browse/DROOLS-5983
Project: Drools
Issue Type: Bug
Components: dmn engine
Reporter: Luca Molteni
Assignee: Matteo Mortari
Verify that indexes are generated correctly.
This should also give some performance different, try measure it with a benchmark.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 3 months
[Red Hat JIRA] (WFLY-14338) JSF: ajax listener not invoked
by Jens a (Jira)
[ https://issues.redhat.com/browse/WFLY-14338?page=com.atlassian.jira.plugi... ]
Jens a commented on WFLY-14338:
-------------------------------
My attached reproducer didn't contain a h:form. Adding the form resolves the issue in the reproducer.
However I still experience the issue in a project where the image tags are within an outputPanel which is within a form.
I will try to create this as a reproducer
> JSF: ajax listener not invoked
> ------------------------------
>
> Key: WFLY-14338
> URL: https://issues.redhat.com/browse/WFLY-14338
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 21.0.2.Final
> Reporter: Jens a
> Assignee: Farah Juma
> Priority: Major
> Attachments: primefaces-test-master.zip
>
>
> Primefaces ajax component doesn't call listener, however the onsuccess and oncomplete JS is executed.
> This issue has been reviewed by the Primefaces team: it is not reproducable on Jetty, so they claim it to be a WildFly specific issue (see full discussion at [https://stackoverflow.com/questions/65810607)]
>
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 3 months
[Red Hat JIRA] (AG-154) Connection leak when DB connection closed during transaction rollback
by Wojciech Kopciewicz (Jira)
[ https://issues.redhat.com/browse/AG-154?page=com.atlassian.jira.plugin.sy... ]
Wojciech Kopciewicz edited comment on AG-154 at 2/1/21 9:08 AM:
----------------------------------------------------------------
Hi [~lbarreiro], the versions are as follows:
- quarkus-jdbc-postgresql-1.9.2.Final
- quarkus-core-1.9.2.Final
was (Author: JIRAUSER149071):
Hi [~lbarreiro], the versions are as follows:
- quarkus-jdbc-postgresql-1.9.2.Final
- quarkus-core-1.9.2.Final
> Connection leak when DB connection closed during transaction rollback
> ---------------------------------------------------------------------
>
> Key: AG-154
> URL: https://issues.redhat.com/browse/AG-154
> Project: Agroal
> Issue Type: Bug
> Components: narayana, pool
> Affects Versions: 1.9
> Reporter: Wojciech Kopciewicz
> Assignee: Luis Barreiro
> Priority: Major
>
> We are using Quarkus 1.9.2 with Hibernate and Agroal to access PostgreSQL DB.
> It looks like Agroal is leaking connections when connection is closed (somewhere) on the server side during transaction rollback.
> The following log was observed:
> Error trying to transactionRollback local transaction: This connection has been closed.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 3 months
[Red Hat JIRA] (AG-154) Connection leak when DB connection closed during transaction rollback
by Wojciech Kopciewicz (Jira)
[ https://issues.redhat.com/browse/AG-154?page=com.atlassian.jira.plugin.sy... ]
Wojciech Kopciewicz commented on AG-154:
----------------------------------------
Hi [~lbarreiro], the versions are as follows:
- quarkus-jdbc-postgresql-1.9.2.Final
- quarkus-core-1.9.2.Final
> Connection leak when DB connection closed during transaction rollback
> ---------------------------------------------------------------------
>
> Key: AG-154
> URL: https://issues.redhat.com/browse/AG-154
> Project: Agroal
> Issue Type: Bug
> Components: narayana, pool
> Affects Versions: 1.9
> Reporter: Wojciech Kopciewicz
> Assignee: Luis Barreiro
> Priority: Major
>
> We are using Quarkus 1.9.2 with Hibernate and Agroal to access PostgreSQL DB.
> It looks like Agroal is leaking connections when connection is closed (somewhere) on the server side during transaction rollback.
> The following log was observed:
> Error trying to transactionRollback local transaction: This connection has been closed.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 3 months
[Red Hat JIRA] (WFLY-14383) Unable to set decay attribute in modcluster subsystem
by Ivan Straka (Jira)
[ https://issues.redhat.com/browse/WFLY-14383?page=com.atlassian.jira.plugi... ]
Ivan Straka updated WFLY-14383:
-------------------------------
Affects Version/s: (was: 23.0.0.Beta1)
> Unable to set decay attribute in modcluster subsystem
> -----------------------------------------------------
>
> Key: WFLY-14383
> URL: https://issues.redhat.com/browse/WFLY-14383
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 22.0.0.Final
> Reporter: Ivan Straka
> Assignee: Ivan Straka
> Priority: Blocker
> Attachments: standalone-full-ha.xml
>
>
> Running with configured mod cluster extension (see attached xml) I get:
> {code:java}
> 13:27:16,733 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 76) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]): java.lang.NumberFormatException: For input string: "2.0"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.parseInt(Integer.java:615)
> at org.jboss.dmr.StringModelValue.asInt(StringModelValue.java:142)
> at org.jboss.dmr.ModelNode.asInt(ModelNode.java:288)
> at org.wildfly.extension.mod_cluster.ModClusterSubsystemServiceHandler.getLoadProvider(ModClusterSubsystemServiceHandler.java:129)
> at org.wildfly.extension.mod_cluster.ModClusterSubsystemServiceHandler.installServices(ModClusterSubsystemServiceHandler.java:95)
> at org.jboss.as.clustering.controller.AddStepHandler.performRuntime(AddStepHandler.java:220)
> at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:343)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:164)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1005)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:744)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> The problem is that the attribute is double, however in add operation handler is parsed as int.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 3 months
[Red Hat JIRA] (WFLY-14384) Unable to set capacity-factor attribute in distributed cache in Infinispan
by Ivan Straka (Jira)
[ https://issues.redhat.com/browse/WFLY-14384?page=com.atlassian.jira.plugi... ]
Ivan Straka updated WFLY-14384:
-------------------------------
Affects Version/s: (was: 23.0.0.Beta1)
> Unable to set capacity-factor attribute in distributed cache in Infinispan
> --------------------------------------------------------------------------
>
> Key: WFLY-14384
> URL: https://issues.redhat.com/browse/WFLY-14384
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 22.0.0.Final
> Reporter: Ivan Straka
> Assignee: Ivan Straka
> Priority: Blocker
> Attachments: standalone-full-ha.xml
>
>
> Running with configured mod cluster extension (see attached xml) I get:
> {code:java}
> 13:27:16,815 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 60) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "infinispan"),
> ("cache-container" => "ejb"),
> ("distributed-cache" => "dist")
> ]): java.lang.NumberFormatException: For input string: "1.0"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.parseInt(Integer.java:615)
> at org.jboss.dmr.StringModelValue.asInt(StringModelValue.java:142)
> at org.jboss.dmr.ModelNode.asInt(ModelNode.java:288)
> at org.jboss.as.clustering.infinispan.subsystem.DistributedCacheServiceConfigurator.configure(DistributedCacheServiceConfigurator.java:53)
> at org.jboss.as.clustering.infinispan.subsystem.CacheServiceHandler.installServices(CacheServiceHandler.java:85)
> at org.jboss.as.clustering.controller.AddStepHandler.performRuntime(AddStepHandler.java:220)
> at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:343)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:164)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1005)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:744)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:513)
> {code}
> The problem is that the attribute is double, however in add operation handler is parsed as int.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 3 months
[Red Hat JIRA] (WFLY-14384) Unable to set capacity-factor attribute in distributed cache in Infinispan
by Ivan Straka (Jira)
[ https://issues.redhat.com/browse/WFLY-14384?page=com.atlassian.jira.plugi... ]
Ivan Straka updated WFLY-14384:
-------------------------------
Attachment: standalone-full-ha.xml
> Unable to set capacity-factor attribute in distributed cache in Infinispan
> --------------------------------------------------------------------------
>
> Key: WFLY-14384
> URL: https://issues.redhat.com/browse/WFLY-14384
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 22.0.0.Final, 23.0.0.Beta1
> Reporter: Ivan Straka
> Assignee: Ivan Straka
> Priority: Blocker
> Attachments: standalone-full-ha.xml
>
>
> Running with configured mod cluster extension (see attached xml) I get:
> {code:java}
> 13:27:16,815 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 60) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "infinispan"),
> ("cache-container" => "ejb"),
> ("distributed-cache" => "dist")
> ]): java.lang.NumberFormatException: For input string: "1.0"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.parseInt(Integer.java:615)
> at org.jboss.dmr.StringModelValue.asInt(StringModelValue.java:142)
> at org.jboss.dmr.ModelNode.asInt(ModelNode.java:288)
> at org.jboss.as.clustering.infinispan.subsystem.DistributedCacheServiceConfigurator.configure(DistributedCacheServiceConfigurator.java:53)
> at org.jboss.as.clustering.infinispan.subsystem.CacheServiceHandler.installServices(CacheServiceHandler.java:85)
> at org.jboss.as.clustering.controller.AddStepHandler.performRuntime(AddStepHandler.java:220)
> at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:343)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:164)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1005)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:744)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:513)
> {code}
> The problem is that the attribute is double, however in add operation handler is parsed as int.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 3 months