May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8410) Test suite depends on the WFCORE-1762 bug

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8410?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-8410: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/9989 > Test suite depends on the WFCORE-1762 bug > ----------------------------------------- > > Key: WFLY-8410 > URL: https://issues.jboss.org/browse/WFLY-8410 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > A number of places in the full WildFly test suite depend on the incorrect behavior that WFCORE-1762 is meant to fix. Tests execute operations that should fail and assume they will succeed. > InterDeploymentDependenciesTestCase and InterDeploymentDependenciesEarTestCase are like this. There may be (many) others. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1762) Missing dependency should be triggering rollback of the deployment operation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1762?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1762: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2374 > Missing dependency should be triggering rollback of the deployment operation > ---------------------------------------------------------------------------- > > Key: WFCORE-1762 > URL: https://issues.jboss.org/browse/WFCORE-1762 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Alpha7 > Reporter: Martin Stefanko > Assignee: Brian Stansberry > > The removal of the deployment which is a dependency for other resources makes these dependent resources unusable. The deployment operation should not be completed in such conditions. > The information about the missing dependencies is now currently logged after the removal by the ContainerStateMonitor class. > Example: > {code}INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment postgresql-9.4.1208.jar (runtime-name: postgresql-9.4.1208.jar) in 61ms > INFO [org.jboss.as.server] (ServerService Thread Pool -- 65) WFLYSRV0009: Undeployed "postgresql-9.4.1208.jar" (runtime-name: "postgresql-9.4.1208.jar") > INFO [org.jboss.as.repository] (ServerService Thread Pool -- 65) WFLYDR0002: Content removed from location /home/mjurc/testing/eap/7.0.0/jboss-eap-7.0/standalone/data/content/5c/7e80698b80a5045fe64daa67426051bbd16a56/content > INFO [org.jboss.as.controller] (ServerService Thread Pool -- 65) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.jdbc-driver.postgresql-9_4_1208_jar (missing) dependents: [service jboss.driver-demander.java:/PostgresDS, service org.wildfly.data-source.PostgresDS] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-95) Test Case - Topology Fails when Linked to Container

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-95?page=com.atlassian.jira.plu... ] Matt Mahoney updated HAWKULARQE-95: ----------------------------------- NOTE BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1446822 > Test Case - Topology Fails when Linked to Container > --------------------------------------------------- > > Key: HAWKULARQE-95 > URL: https://issues.jboss.org/browse/HAWKULARQE-95 > Project: Hawkular QE > Issue Type: Feature Request > Reporter: Matt Mahoney > Assignee: Michael Foley > > Do we have a test case for the following? > " topology view fails once I have a server linked to a container" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1542) Root cause Exception is hidden in MVELExprAnalyzer.analyzeExpression()

by Toshiya Kobayashi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1542?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi edited comment on DROOLS-1542 at 5/1/17 6:40 AM: ------------------------------------------------------------------- Ah, RuntimeException is explicitly re-thrown. So probably only in case of Error. But I'm not 100% sure. https://github.com/mvel/mvel/blob/mvel2-2.2.8.Final/src/main/java/org/mve... I guess logging in Drools side is preferred anyway... was (Author: tkobayashi): Ah, RuntimeException is explicitly re-thrown. So probably only in case of Error. https://github.com/mvel/mvel/blob/mvel2-2.2.8.Final/src/main/java/org/mve... > Root cause Exception is hidden in MVELExprAnalyzer.analyzeExpression() > ---------------------------------------------------------------------- > > Key: DROOLS-1542 > URL: https://issues.jboss.org/browse/DROOLS-1542 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.CR2 > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > Labels: support > > When an Error/-RuntimeException- is thrown in MVEL via MVELExprAnalyzer.analyzeExpression(), the root cause Error/-RuntimeException- is not propagated nor logged. For example, if it was StackOverflowError, it's hard to identify the root cause. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1542) Root cause Exception is hidden in MVELExprAnalyzer.analyzeExpression()

by Toshiya Kobayashi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1542?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi updated DROOLS-1542: -------------------------------------- Description: When an Error/-RuntimeException- is thrown in MVEL via MVELExprAnalyzer.analyzeExpression(), the root cause Error/-RuntimeException- is not propagated nor logged. For example, if it was StackOverflowError, it's hard to identify the root cause. (was: When an Error/RuntimeException is thrown in MVEL via MVELExprAnalyzer.analyzeExpression(), the root cause Error/RuntimeException is not propagated nor logged. For example, if it was StackOverflowError, it's hard to identify the root cause.) > Root cause Exception is hidden in MVELExprAnalyzer.analyzeExpression() > ---------------------------------------------------------------------- > > Key: DROOLS-1542 > URL: https://issues.jboss.org/browse/DROOLS-1542 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.CR2 > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > Labels: support > > When an Error/-RuntimeException- is thrown in MVEL via MVELExprAnalyzer.analyzeExpression(), the root cause Error/-RuntimeException- is not propagated nor logged. For example, if it was StackOverflowError, it's hard to identify the root cause. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1542) Root cause Exception is hidden in MVELExprAnalyzer.analyzeExpression()

by Toshiya Kobayashi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1542?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi commented on DROOLS-1542: ------------------------------------------- Ah, RuntimeException is explicitly re-thrown. So probably only in case of Error. https://github.com/mvel/mvel/blob/mvel2-2.2.8.Final/src/main/java/org/mve... > Root cause Exception is hidden in MVELExprAnalyzer.analyzeExpression() > ---------------------------------------------------------------------- > > Key: DROOLS-1542 > URL: https://issues.jboss.org/browse/DROOLS-1542 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.CR2 > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > Labels: support > > When an Error/RuntimeException is thrown in MVEL via MVELExprAnalyzer.analyzeExpression(), the root cause Error/RuntimeException is not propagated nor logged. For example, if it was StackOverflowError, it's hard to identify the root cause. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1542) Root cause Exception is hidden in MVELExprAnalyzer.analyzeExpression()

by Toshiya Kobayashi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1542?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi updated DROOLS-1542: -------------------------------------- Git Pull Request: https://github.com/kiegroup/drools/pull/1234 > Root cause Exception is hidden in MVELExprAnalyzer.analyzeExpression() > ---------------------------------------------------------------------- > > Key: DROOLS-1542 > URL: https://issues.jboss.org/browse/DROOLS-1542 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.CR2 > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > Labels: support > > When an Error/RuntimeException is thrown in MVEL via MVELExprAnalyzer.analyzeExpression(), the root cause Error/RuntimeException is not propagated nor logged. For example, if it was StackOverflowError, it's hard to identify the root cause. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1542) Root cause Exception is hidden in MVELExprAnalyzer.analyzeExpression()

by Toshiya Kobayashi (JIRA)

Toshiya Kobayashi created DROOLS-1542: ----------------------------------------- Summary: Root cause Exception is hidden in MVELExprAnalyzer.analyzeExpression() Key: DROOLS-1542 URL: https://issues.jboss.org/browse/DROOLS-1542 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.0.0.CR2 Reporter: Toshiya Kobayashi Assignee: Mario Fusco When an Error/RuntimeException is thrown in MVEL via MVELExprAnalyzer.analyzeExpression(), the root cause Error/RuntimeException is not propagated nor logged. For example, if it was StackOverflowError, it's hard to identify the root cause. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

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 May 2017