October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1349) Eager evaluation with no-loop causes endless loop

by Petr Široký (JIRA)

Petr Široký created DROOLS-1349: ----------------------------------- Summary: Eager evaluation with no-loop causes endless loop Key: DROOLS-1349 URL: https://issues.jboss.org/browse/DROOLS-1349 Project: Drools Issue Type: Bug Components: core engine Reporter: Petr Široký Assignee: Mario Fusco Using {{no-loop}} with eager evaluation does not work as expected. The {{no-loop}} rule keeps firing in endless loop. This test case in jBPM reproduces the issue https://github.com/droolsjbpm/jbpm/blob/master/jbpm-bpmn2/src/test/java/o... (testBusinessRuleTaskDynamic). -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1349) Eager evaluation with no-loop causes endless loop

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1349?page=com.atlassian.jira.plugi... ] Petr Široký updated DROOLS-1349: -------------------------------- Description: Using {{no-loop}} with eager evaluation does not work as expected. The {{no-loop}} rule keeps firing in endless loop. This test case in jBPM reproduces the issue https://github.com/droolsjbpm/jbpm/blob/6.5.x/jbpm-bpmn2/src/test/java/or... (testBusinessRuleTaskDynamic). was: Using {{no-loop}} with eager evaluation does not work as expected. The {{no-loop}} rule keeps firing in endless loop. This test case in jBPM reproduces the issue https://github.com/droolsjbpm/jbpm/blob/master/jbpm-bpmn2/src/test/java/o... (testBusinessRuleTaskDynamic). > Eager evaluation with no-loop causes endless loop > ------------------------------------------------- > > Key: DROOLS-1349 > URL: https://issues.jboss.org/browse/DROOLS-1349 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Petr Široký > Assignee: Mario Fusco > > Using {{no-loop}} with eager evaluation does not work as expected. The {{no-loop}} rule keeps firing in endless loop. > This test case in jBPM reproduces the issue https://github.com/droolsjbpm/jbpm/blob/6.5.x/jbpm-bpmn2/src/test/java/or... (testBusinessRuleTaskDynamic). -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1903) Slaves receiving an exception during registration hang and don't exit

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1903?page=com.atlassian.jira.plugi... ] Ken Wills commented on WFCORE-1903: ----------------------------------- Accidently tested against wrong branch, so not really a bug. > Slaves receiving an exception during registration hang and don't exit > --------------------------------------------------------------------- > > Key: WFCORE-1903 > URL: https://issues.jboss.org/browse/WFCORE-1903 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Ken Wills > Assignee: Ken Wills > > Existing PR here: https://github.com/wildfly/wildfly-core/pull/1881 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1903) Slaves receiving an exception during registration hang and don't exit

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1903?page=com.atlassian.jira.plugi... ] Ken Wills closed WFCORE-1903. ----------------------------- Resolution: Cannot Reproduce Bug > Slaves receiving an exception during registration hang and don't exit > --------------------------------------------------------------------- > > Key: WFCORE-1903 > URL: https://issues.jboss.org/browse/WFCORE-1903 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Ken Wills > Assignee: Ken Wills > > Existing PR here: https://github.com/wildfly/wildfly-core/pull/1881 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1904) Enviroment variable DEBUG_PORT doesn't work with standalone.bat

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1904?page=com.atlassian.jira.plugi... ] Tomaz Cerar deleted WFCORE-1904: -------------------------------- > Enviroment variable DEBUG_PORT doesn't work with standalone.bat > --------------------------------------------------------------- > > Key: WFCORE-1904 > URL: https://issues.jboss.org/browse/WFCORE-1904 > Project: WildFly Core > Issue Type: Bug > Environment: windows > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > This issue is blocked by JBEAP-5551 in 7.1.0.DR2. But I fixed standalone.conf.bat locally (I used fix from PR from JBEAP-5551) and port still can't be changed by env variable, see this example: > {noformat} > set DEBUG=true > set DEBUG_PORT=7878 > C:\Users\Administrator\playground\7.1.0.DR2\jboss-eap-7.1\bin>standalone.bat > Calling "C:\Users\Administrator\playground\7.1.0.DR2\jboss-eap-7.1\bin\standalone.conf.bat" > Setting JAVA property to "C:\jdk1.8.0_45\bin\java" > =============================================================================== > JBoss Bootstrap Environment > JBOSS_HOME: "C:\Users\Administrator\playground\7.1.0.DR2\jboss-eap-7.1" > JAVA: "C:\jdk1.8.0_45\bin\java" > JAVA_OPTS: "-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogF > ileSize=3M -Xloggc: -XX:-TraceClassUnloading -Dprogram.name=standalone.bat -Xms1G -Xmx1G -XX:MetaspaceSize=96M -XX:MaxMetaspaceSiz > e=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -agentlib:jdwp=transport=dt_socket,address=87 > 87,server=y,suspend=n" > =============================================================================== > Listening for transport dt_socket at address: 8787 > {noformat} > 8787 port is used. 7878 port should be used in this example. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7407) split artemis journal in its own module

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-7407: --------------------------------- Summary: split artemis journal in its own module Key: WFLY-7407 URL: https://issues.jboss.org/browse/WFLY-7407 Project: WildFly Issue Type: Enhancement Components: JMS Affects Versions: 10.0.0.CR2 Reporter: Jeff Mesnil Assignee: Jeff Mesnil Priority: Minor Fix For: 11.0.0.Alpha1 The org.jboss.jts is depending on the org.apache.activemq.artemis only for its journal functionality but get all the module dependencies (including messaging stuff) that is not used at all. The org.apache.activemq.artemis should be split with a separate module for its journal containing the journal jar + commons jar + native lib required for libAIO. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1904) Enviroment variable DEBUG_PORT doesn't work with standalone.bat

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-1904: ----------------------------------- Summary: Enviroment variable DEBUG_PORT doesn't work with standalone.bat Key: WFCORE-1904 URL: https://issues.jboss.org/browse/WFCORE-1904 Project: WildFly Core Issue Type: Bug Components: Scripts Environment: windows Reporter: Tomaz Cerar Assignee: Tomaz Cerar Fix For: 3.0.0.Alpha11 This issue is blocked by JBEAP-5551 in 7.1.0.DR2. But I fixed standalone.conf.bat locally (I used fix from PR from JBEAP-5551) and port still can't be changed by env variable, see this example: {noformat} set DEBUG=true set DEBUG_PORT=7878 C:\Users\Administrator\playground\7.1.0.DR2\jboss-eap-7.1\bin>standalone.bat Calling "C:\Users\Administrator\playground\7.1.0.DR2\jboss-eap-7.1\bin\standalone.conf.bat" Setting JAVA property to "C:\jdk1.8.0_45\bin\java" =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: "C:\Users\Administrator\playground\7.1.0.DR2\jboss-eap-7.1" JAVA: "C:\jdk1.8.0_45\bin\java" JAVA_OPTS: "-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogF ileSize=3M -Xloggc: -XX:-TraceClassUnloading -Dprogram.name=standalone.bat -Xms1G -Xmx1G -XX:MetaspaceSize=96M -XX:MaxMetaspaceSiz e=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -agentlib:jdwp=transport=dt_socket,address=87 87,server=y,suspend=n" =============================================================================== Listening for transport dt_socket at address: 8787 {noformat} 8787 port is used. 7878 port should be used in this example. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1903) Slaves receiving an exception during registration hang and don't exit

by Ken Wills (JIRA)

Ken Wills created WFCORE-1903: --------------------------------- Summary: Slaves receiving an exception during registration hang and don't exit Key: WFCORE-1903 URL: https://issues.jboss.org/browse/WFCORE-1903 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Ken Wills Assignee: Ken Wills Existing PR here: https://github.com/wildfly/wildfly-core/pull/1881 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7406) Cleanup HornetQ xsd files in "docs/schema" directory

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-7406: --------------------------------- Summary: Cleanup HornetQ xsd files in "docs/schema" directory Key: WFLY-7406 URL: https://issues.jboss.org/browse/WFLY-7406 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 10.0.0.CR4 Reporter: Jeff Mesnil Assignee: Jeff Mesnil Priority: Minor The download zip for WildFly 10.0CR4 contains the xsd files for HornetQ messaging configurations in "docs/schema". Those are obsoleted by ActiveMQ and should be removed. -jboss-as-messaging-deployment_1_0.xsd (deployment of a "-jms.xml" file according to this old schema will fail with an error anyway), replaced by "wildfly-messaging-activemq-deployment_1_0.xsd") -jboss-as-messaging_x_y.xsd (server configuration files, replaced by "wildfly-messaging-activemq_1_0.xsd"). -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1347) Explicit expiration of event not effective - regression from 6.4 to 6.5

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1347?page=com.atlassian.jira.plugi... ] Matteo Mortari reassigned DROOLS-1347: -------------------------------------- Assignee: Matteo Mortari (was: Mario Fusco) > Explicit expiration of event not effective - regression from 6.4 to 6.5 > ----------------------------------------------------------------------- > > Key: DROOLS-1347 > URL: https://issues.jboss.org/browse/DROOLS-1347 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final > Reporter: Thibault Daoulas > Assignee: Matteo Mortari > > I just ugraded my project from Drools 6.4.0.Final to 6.5.0.Final and have now quite a few tests on rules that fail, all have in common that they test the expiration of events, where an event that should have been removed from the working memory is still present. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2016