December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2356) Failure in a step ResultHandler should not always be reported as occurring during rollback

by Katarina Hermanova (Jira)

[ https://issues.jboss.org/browse/WFCORE-2356?page=com.atlassian.jira.plugi... ] Katarina Hermanova reassigned WFCORE-2356: ------------------------------------------ Assignee: Katarina Hermanova > Failure in a step ResultHandler should not always be reported as occurring during rollback > ------------------------------------------------------------------------------------------ > > Key: WFCORE-2356 > URL: https://issues.jboss.org/browse/WFCORE-2356 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Brian Stansberry > Assignee: Katarina Hermanova > Priority: Minor > > When AbstractOperationContext.Step invokes a ResultHandler it catches and logs any exception. But the logged message states that the catch was during rollback handling. When the code was first written, perhaps the catch block was only for rollback handling, but now it handles both rollback and completion of successful ops. So the log message needs to be accurate. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4767) Use descriptive error message for duplicate host/context deployments

by Katarina Hermanova (Jira)

[ https://issues.jboss.org/browse/WFCORE-4767?page=com.atlassian.jira.plugi... ] Katarina Hermanova updated WFCORE-4767: --------------------------------------- Component/s: Server > Use descriptive error message for duplicate host/context deployments > -------------------------------------------------------------------- > > Key: WFCORE-4767 > URL: https://issues.jboss.org/browse/WFCORE-4767 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Paul Ferraro > Assignee: Katarina Hermanova > Priority: Minor > > If a user attempts to deploy a web application to a host/context to which another application is deployed, this will fail for obvious reasons. > What isn't obvious is the error message. Currently, users will see a DuplicateServiceException. Ideally, the error message should indicate that another application is deployed for the same host and context path. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4767) Use descriptive error message for duplicate host/context deployments

by Katarina Hermanova (Jira)

[ https://issues.jboss.org/browse/WFCORE-4767?page=com.atlassian.jira.plugi... ] Katarina Hermanova moved WFLY-4051 to WFCORE-4767: -------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4767 (was: WFLY-4051) Component/s: (was: Web (Undertow)) Affects Version/s: (was: 9.0.0.Alpha1) > Use descriptive error message for duplicate host/context deployments > -------------------------------------------------------------------- > > Key: WFCORE-4767 > URL: https://issues.jboss.org/browse/WFCORE-4767 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Paul Ferraro > Assignee: Katarina Hermanova > Priority: Minor > > If a user attempts to deploy a web application to a host/context to which another application is deployed, this will fail for obvious reasons. > What isn't obvious is the error message. Currently, users will see a DuplicateServiceException. Ideally, the error message should indicate that another application is deployed for the same host and context path. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12837) Use descriptive error message for duplicate host/context deployments

by Katarina Hermanova (Jira)

Katarina Hermanova created WFLY-12837: ----------------------------------------- Summary: Use descriptive error message for duplicate host/context deployments Key: WFLY-12837 URL: https://issues.jboss.org/browse/WFLY-12837 Project: WildFly Issue Type: Enhancement Components: Web (Undertow) Affects Versions: 9.0.0.Alpha1 Reporter: Katarina Hermanova Assignee: Katarina Hermanova If a user attempts to deploy a web application to a host/context to which another application is deployed, this will fail for obvious reasons. What isn't obvious is the error message. Currently, users will see a DuplicateServiceException. Ideally, the error message should indicate that another application is deployed for the same host and context path. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4827) Refactoring Test Tool data population

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4827?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4827: ------------------------------- Story Points: 1 > Refactoring Test Tool data population > ------------------------------------- > > Key: DROOLS-4827 > URL: https://issues.jboss.org/browse/DROOLS-4827 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Minor > Labels: TestScenario > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4761) Move kie-remote and hacep module into drools repo

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4761?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4761: --------------------------------------- Sprint: 2019 Week 50-52 (from Dec 9) > Move kie-remote and hacep module into drools repo > ------------------------------------------------- > > Key: DROOLS-4761 > URL: https://issues.jboss.org/browse/DROOLS-4761 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4761) Move kie-remote and hacep module into drools repo

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4761?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4761: --------------------------------------- Sprint: 2019 Week 47-49 (from Nov 18) (was: 2019 Week 50-52 (from Dec 9)) > Move kie-remote and hacep module into drools repo > ------------------------------------------------- > > Key: DROOLS-4761 > URL: https://issues.jboss.org/browse/DROOLS-4761 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-482) Add log4j2 support for WildFly

by Andrew Marlow (Jira)

[ https://issues.jboss.org/browse/WFCORE-482?page=com.atlassian.jira.plugin... ] Andrew Marlow commented on WFCORE-482: -------------------------------------- In my previous comment I got it slightly wrong regarding my mention of CVEs. There is only one CVE and it is not even filed against log4j-v1. There is CVE-2017-5645 which is logged against log4j2. It is to do with the code that listens on the logger event port and deserialises without doing some sanity checking. Diffing between 2.8.1 and 2.8.2 I see how checking has now been added. The code is slightly different in v1 but it does still perform an unchecked deserialisation of a LoggerEvent object, so it does look vulnerable to me. There may be a new CVE raised for this at some point, even though log4j-v1 is end of life. I hope a new CVE is raised. The lack of a current CVE for log4j-v1 is causing some people to say that when they are alerted to CVE-2017-5645 it is a false flag. See https://github.com/jeremylong/DependencyCheck/issues/1138 for an example of this. I think that Red Hat has performed the same code analysis that I did and come to the same conclusion, which is why they patched JBoss (the proprietary version of Wildfly). So it might not be viewed as a false flag forever. I've chased down the log4j-v1 dependency. It comes from jbossws-cxf-client. So I reckon that would have to be changed to use log4j2 before wildfly could be changed. I think a new ticket needs to be raised for jbossws-cxf-client. > Add log4j2 support for WildFly > ------------------------------ > > Key: WFCORE-482 > URL: https://issues.jboss.org/browse/WFCORE-482 > Project: WildFly Core > Issue Type: Task > Components: Logging > Environment: Spring 3, Hibernate, Wicket, JBoss AS7 > Reporter: Amarkanth Ranganamayna > Assignee: James Perkins > Priority: Major > > I am trying to use Flume Appender which comes with Log4j2 (log4j 1.x doesn't support flume appender) (AND) inorder to acheive this, I am looking at how to configure JBoss AS7 to use log4j2. > Looks like Jboss AS7 by default use log4j 1.x > Are you guys already working on using log4j2 ? > If NOT, can you please suggest how to configure Jboss AS7 such that it picks up "log4j2.xml" file and doesn't use its own logging. > Thanks, > Amar -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4829) Rule with NotNode in the middle is not fired after ksession.reset()

by Toshiya Kobayashi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4829?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi updated DROOLS-4829: -------------------------------------- Git Pull Request: https://github.com/kiegroup/drools/pull/2667 > Rule with NotNode in the middle is not fired after ksession.reset() > ------------------------------------------------------------------- > > Key: DROOLS-4829 > URL: https://issues.jboss.org/browse/DROOLS-4829 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.30.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > Labels: support > > When a rule has "not" in the middle of LHS patterns, the rule is not fired after disposing a ksession from KieSessionsPool (= ksession.reset()). > This is a slightly different scenario from DROOLS-3228. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4829) Rule with NotNode in the middle is not fired after ksession.reset()

by Toshiya Kobayashi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4829?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi reassigned DROOLS-4829: ----------------------------------------- Assignee: Toshiya Kobayashi (was: Mario Fusco) > Rule with NotNode in the middle is not fired after ksession.reset() > ------------------------------------------------------------------- > > Key: DROOLS-4829 > URL: https://issues.jboss.org/browse/DROOLS-4829 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.30.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > Labels: support > > When a rule has "not" in the middle of LHS patterns, the rule is not fired after disposing a ksession from KieSessionsPool (= ksession.reset()). > This is a slightly different scenario from DROOLS-3228. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 December 2019