October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3072) kie-maven-plugin to persist DMN Compilation results in KJAR like for DRL exec model rules

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3072: -------------------------------------- Summary: kie-maven-plugin to persist DMN Compilation results in KJAR like for DRL exec model rules Key: DROOLS-3072 URL: https://issues.jboss.org/browse/DROOLS-3072 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Edson Tirelli -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3071) Some DMN TCK test are not compiling correctly with exec model

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3071: -------------------------------------- Summary: Some DMN TCK test are not compiling correctly with exec model Key: DROOLS-3071 URL: https://issues.jboss.org/browse/DROOLS-3071 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Edson Tirelli -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3070) Ensure DMN JUnit tests in modules are parametrized for running also for compilation with exec model

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3070: -------------------------------------- Summary: Ensure DMN JUnit tests in modules are parametrized for running also for compilation with exec model Key: DROOLS-3070 URL: https://issues.jboss.org/browse/DROOLS-3070 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Edson Tirelli -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections

by Jan-Willem Gmelig Meyling (Jira)

[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ] Jan-Willem Gmelig Meyling commented on WFLY-10531: -------------------------------------------------- Hi [~jondruse], I have been trying to construct a reproducer myself as well. Apparently this is quite an edge case, because even with some background knowledge about the situation I am trying to create, I have failed to reproduce it so far. I know at least one "broken" use case of JMSContext must exist in my code base, because I am suffering from the issue, but I've failed to isolate it so far. From looking at the code the fix must be sufficient, but I just can't imagine why the situation would occur in the first place. I am also wondering whether we aren't creating new instances of WFLY-9501. My current belief is that we might incorrectly think that the inTX() check is to blame, and that perhaps the issue is that the resource is added under a conflicting name, henceforth thinks a clean up listener is already added and just ignores the new JMSContext? I am thinking for example about sub transactions (i.e. an EJB method entering an EJB TX within a CDI TX or an EJB entering a method with transaction NEW mode). Do they share resources with the "parent" tx? Anyway, I'd would like to create a reproducer test case so we can gather some confidence in whether this implementation solves both WFLY-10531 and WFLY-9501 in all cases :) I'll invest some time in it too, see what I can come up with. > Wildfly leaks ActiveMQ connections > ---------------------------------- > > Key: WFLY-10531 > URL: https://issues.jboss.org/browse/WFLY-10531 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Environment: openjdk 8 / openjdk 9, Linux > Reporter: Marcel Šebek > Assignee: Jeff Mesnil > Priority: Major > Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip > > > After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on > IJ000453: Unable to get managed connection for java:/JmsXA > and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log: > WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69) > Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time. > It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3069) DMN kie-dmn-tck runner is not passing down property `compiler.execmodel`

by Tibor Zimányi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3069?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-3069: ---------------------------------- Story Points: 2 (was: 3) > DMN kie-dmn-tck runner is not passing down property `compiler.execmodel` > ------------------------------------------------------------------------- > > Key: DROOLS-3069 > URL: https://issues.jboss.org/browse/DROOLS-3069 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Tibor Zimányi > Priority: Major > > To enable exec model DMN compilation, property `org.kie.dmn.compiler.execmodel` is used. > However kie-dmn-tck runner is ignoring this property and not passed down while running the TCK test from this module. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3069) DMN kie-dmn-tck runner is not passing down property `compiler.execmodel`

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3069: -------------------------------------- Summary: DMN kie-dmn-tck runner is not passing down property `compiler.execmodel` Key: DROOLS-3069 URL: https://issues.jboss.org/browse/DROOLS-3069 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Tibor Zimányi To enable exec model DMN compilation, property `org.kie.dmn.compiler.execmodel` is used. However kie-dmn-tck runner is ignoring this property and not passed down while running the TCK test from this module. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11058) Quickstarts Spring 5 Update

by Tomas Repel (Jira)

[ https://issues.jboss.org/browse/WFLY-11058?page=com.atlassian.jira.plugin... ] Tomas Repel commented on WFLY-11058: ------------------------------------ [~emmartins], [~mjurc] I don't have a strong opinion here. If the Quickstarts works I think it is ok to have Spring 5 as default profile. Spring is a huge ecosystem, it is impossible to have guarantee that it works on WFLY properly all over (regardless EAP7-693). > Quickstarts Spring 5 Update > --------------------------- > > Key: WFLY-11058 > URL: https://issues.jboss.org/browse/WFLY-11058 > Project: WildFly > Issue Type: Enhancement > Components: Quickstarts > Affects Versions: 14.0.0.Final > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > The following quickstarts should be updated to work with Spring 5: > * spring-greeter > * spring-kitchensink-basic > * spring-kitchensink-springmvctest > * spring-resteasy -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3068) Follows-up on DROOLS-1701 to ensure DMN Compilation passes test in suites

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3068?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-3068: ----------------------------------- Description: Follows-up on DROOLS-1701 to ensure DMN Compilation passes test in suites > Follows-up on DROOLS-1701 to ensure DMN Compilation passes test in suites > ------------------------------------------------------------------------- > > Key: DROOLS-3068 > URL: https://issues.jboss.org/browse/DROOLS-3068 > Project: Drools > Issue Type: Epic > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Follows-up on DROOLS-1701 to ensure DMN Compilation passes test in suites -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3068) DMN Compilation test e2e

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3068?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-3068: ----------------------------------- Summary: DMN Compilation test e2e (was: Follows-up on DROOLS-1701 to ensure DMN Compilation passes test in suites) > DMN Compilation test e2e > ------------------------ > > Key: DROOLS-3068 > URL: https://issues.jboss.org/browse/DROOLS-3068 > Project: Drools > Issue Type: Epic > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Follows-up on DROOLS-1701 to ensure DMN Compilation passes test in suites -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3068) Follows-up on DROOLS-1701 to ensure DMN Compilation passes test in suites

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3068: -------------------------------------- Summary: Follows-up on DROOLS-1701 to ensure DMN Compilation passes test in suites Key: DROOLS-3068 URL: https://issues.jboss.org/browse/DROOLS-3068 Project: Drools Issue Type: Epic Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018