January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2227) Verifier should manage predicate columns properly

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2227?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-2227: --------------------------------- Description: < Rikkola> for dtables, string comparison is probably enough, prooobably < Rikkola> and when I type that nope < Rikkola> eval( 1+1) and eval( 0+2) are the same, but no way to know < Rikkola> maybe a warning when columns like this are used, the V&V might not pick everything up > Verifier should manage predicate columns properly > ------------------------------------------------- > > Key: DROOLS-2227 > URL: https://issues.jboss.org/browse/DROOLS-2227 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > > < Rikkola> for dtables, string comparison is probably enough, > prooobably > < Rikkola> and when I type that nope > < Rikkola> eval( 1+1) and eval( 0+2) are the same, but no way to know > < Rikkola> maybe a warning when columns like this are used, the V&V might > not pick everything up -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2227) Verifier should manage predicate columns properly

by Toni Rikkola (JIRA)

Toni Rikkola created DROOLS-2227: ------------------------------------ Summary: Verifier should manage predicate columns properly Key: DROOLS-2227 URL: https://issues.jboss.org/browse/DROOLS-2227 Project: Drools Issue Type: Enhancement Components: Guided Decision Table Editor Reporter: Toni Rikkola Assignee: Toni Rikkola -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2227) Verifier should manage predicate columns properly

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2227?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-2227: -------------------------------------- ping [~jomarko] > Verifier should manage predicate columns properly > ------------------------------------------------- > > Key: DROOLS-2227 > URL: https://issues.jboss.org/browse/DROOLS-2227 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3502) Fix debug options in test-runner

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3502?page=com.atlassian.jira.plugi... ] Marek Kopecký updated WFCORE-3502: ---------------------------------- Affects Version/s: 4.0.0.Alpha5 > Fix debug options in test-runner > -------------------------------- > > Key: WFCORE-3502 > URL: https://issues.jboss.org/browse/WFCORE-3502 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 4.0.0.Alpha5 > Reporter: Marek Kopecký > Assignee: Marek Kopecký > > Test-runner doesn't handle debug options correctly. > If jdpa profile is used, surefire jvm uses this JVM attribute: {{-agentlib:jdwp=transport=dt_socket,address=$\{as.debug.port\},server=y,suspend=y}}. > The same attribute is passed to started server. But server debugging should be set by {{wildfly.debug}} and {{wildfly.debug.port}} java properties. So if user wants to debug surefire with 8787 port and server with 8786 port, user uses jdpa profile, {{wildfly.debug}} property and {{wildfly.debug.port}} property and test fails: > {{mvn test -DfailIfNoTests=false -DtestLogToFile=false -Dtest=CdTestCase -Djpda -Dwildfly.debug=true -Dwildfly.debug.port=8786}} > {noformat} > ERROR: Cannot load this JVM TI agent twice, check your java command line for duplicate jdwp options. > Error occurred during initialization of VM > agent library failed to init: jdwp > Running null > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3502) Fix debug options in test-runner

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3502?page=com.atlassian.jira.plugi... ] Marek Kopecký updated WFCORE-3502: ---------------------------------- Description: Test-runner doesn't handle debug options correctly. If jdpa profile is used, surefire jvm uses this JVM attribute: {{-agentlib:jdwp=transport=dt_socket,address=$\{as.debug.port\},server=y,suspend=y}}. The same attribute is passed to started server. But server debugging should be set by {{wildfly.debug}} and {{wildfly.debug.port}} java properties. So if user wants to debug surefire with 8787 port and server with 8786 port, user uses jdpa profile, {{wildfly.debug}} property and {{wildfly.debug.port}} property and test fails: {{mvn test -DfailIfNoTests=false -DtestLogToFile=false -Dtest=CdTestCase -Djpda -Dwildfly.debug=true -Dwildfly.debug.port=8786}} {noformat} ERROR: Cannot load this JVM TI agent twice, check your java command line for duplicate jdwp options. Error occurred during initialization of VM agent library failed to init: jdwp Running null {noformat} was: Test-runner doesn't handle debug options correctly. If jdpa profile is used, surefire jvm uses this JVM attribute: {{-agentlib:jdwp=transport=dt_socket,address=$\{as.debug.port\},server=y,suspend=y}}. The same attribute is passed to started server. But server debugging should be set by {{wildfly.debug}} and {{wildfly.debug.port}} java properties. So if user wants to debug surefire with 8787 port and server with 8786 port, he uses jdpa profile, {{wildfly.debug}} property and {{wildfly.debug.port}} property and test fails: {{mvn test -DfailIfNoTests=false -DtestLogToFile=false -Dtest=CdTestCase -Djpda -Dwildfly.debug=true -Dwildfly.debug.port=8786}} {noformat} ERROR: Cannot load this JVM TI agent twice, check your java command line for duplicate jdwp options. Error occurred during initialization of VM agent library failed to init: jdwp Running null {noformat} > Fix debug options in test-runner > -------------------------------- > > Key: WFCORE-3502 > URL: https://issues.jboss.org/browse/WFCORE-3502 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Marek Kopecký > Assignee: Marek Kopecký > > Test-runner doesn't handle debug options correctly. > If jdpa profile is used, surefire jvm uses this JVM attribute: {{-agentlib:jdwp=transport=dt_socket,address=$\{as.debug.port\},server=y,suspend=y}}. > The same attribute is passed to started server. But server debugging should be set by {{wildfly.debug}} and {{wildfly.debug.port}} java properties. So if user wants to debug surefire with 8787 port and server with 8786 port, user uses jdpa profile, {{wildfly.debug}} property and {{wildfly.debug.port}} property and test fails: > {{mvn test -DfailIfNoTests=false -DtestLogToFile=false -Dtest=CdTestCase -Djpda -Dwildfly.debug=true -Dwildfly.debug.port=8786}} > {noformat} > ERROR: Cannot load this JVM TI agent twice, check your java command line for duplicate jdwp options. > Error occurred during initialization of VM > agent library failed to init: jdwp > Running null > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3502) Fix debug options in test-runner

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3502?page=com.atlassian.jira.plugi... ] Marek Kopecký updated WFCORE-3502: ---------------------------------- Summary: Fix debug options in test-runner (was: Test-runner doesn't handle debug options correctly) > Fix debug options in test-runner > -------------------------------- > > Key: WFCORE-3502 > URL: https://issues.jboss.org/browse/WFCORE-3502 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Marek Kopecký > Assignee: Marek Kopecký > > Test-runner doesn't handle debug options correctly. > If jdpa profile is used, surefire jvm uses this JVM attribute: {{-agentlib:jdwp=transport=dt_socket,address=$\{as.debug.port\},server=y,suspend=y}}. > The same attribute is passed to started server. But server debugging should be set by {{wildfly.debug}} and {{wildfly.debug.port}} java properties. So if user wants to debug surefire with 8787 port and server with 8786 port, he uses jdpa profile, {{wildfly.debug}} property and {{wildfly.debug.port}} property and test fails: > {{mvn test -DfailIfNoTests=false -DtestLogToFile=false -Dtest=CdTestCase -Djpda -Dwildfly.debug=true -Dwildfly.debug.port=8786}} > {noformat} > ERROR: Cannot load this JVM TI agent twice, check your java command line for duplicate jdwp options. > Error occurred during initialization of VM > agent library failed to init: jdwp > Running null > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3502) Test-runner doesn't handle debug options correctly

by Marek Kopecký (JIRA)

Marek Kopecký created WFCORE-3502: ------------------------------------- Summary: Test-runner doesn't handle debug options correctly Key: WFCORE-3502 URL: https://issues.jboss.org/browse/WFCORE-3502 Project: WildFly Core Issue Type: Bug Components: Test Suite Reporter: Marek Kopecký Assignee: Marek Kopecký Test-runner doesn't handle debug options correctly. If jdpa profile is used, surefire jvm uses this JVM attribute: {{-agentlib:jdwp=transport=dt_socket,address=$\{as.debug.port\},server=y,suspend=y}}. The same attribute is passed to started server. But server debugging should be set by {{wildfly.debug}} and {{wildfly.debug.port}} java properties. So if user wants to debug surefire with 8787 port and server with 8786 port, he uses jdpa profile, {{wildfly.debug}} property and {{wildfly.debug.port}} property and test fails: {{mvn test -DfailIfNoTests=false -DtestLogToFile=false -Dtest=CdTestCase -Djpda -Dwildfly.debug=true -Dwildfly.debug.port=8786}} {noformat} ERROR: Cannot load this JVM TI agent twice, check your java command line for duplicate jdwp options. Error occurred during initialization of VM agent library failed to init: jdwp Running null {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2211) Trying to modify a global wm object from the consequence of a rule belonging to rule unit causes a NPE

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2211?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2211: -------------------------------- Sprint: 2018 Week 01-02 > Trying to modify a global wm object from the consequence of a rule belonging to rule unit causes a NPE > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-2211 > URL: https://issues.jboss.org/browse/DROOLS-2211 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2208) Sometimes the agenda stops firing even if there are outstanding activations to be evaluated

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2208?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2208: -------------------------------- Sprint: 2018 Week 01-02 > Sometimes the agenda stops firing even if there are outstanding activations to be evaluated > ------------------------------------------------------------------------------------------- > > Key: DROOLS-2208 > URL: https://issues.jboss.org/browse/DROOLS-2208 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2209) Error with accumulator and DataSource being used in rule units

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2209?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2209: -------------------------------- Sprint: 2018 Week 01-02 > Error with accumulator and DataSource being used in rule units > -------------------------------------------------------------- > > Key: DROOLS-2209 > URL: https://issues.jboss.org/browse/DROOLS-2209 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 January 2018