February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBLOGGING-131) Logger.getEffectiveLevel() not working correctly

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-131?page=com.atlassian.jira.plu... ] Ingo Weiss reassigned JBLOGGING-131: ------------------------------------ Assignee: James Perkins (was: Ingo Weiss) > Logger.getEffectiveLevel() not working correctly > ------------------------------------------------ > > Key: JBLOGGING-131 > URL: https://issues.jboss.org/browse/JBLOGGING-131 > Project: JBoss Logging > Issue Type: Bug > Components: jboss-logging-log4j > Reporter: Ingo Weiss > Assignee: James Perkins > Priority: Minor > > The Logger.getEffectiveLevel() method doesn't seem to return correct values. > In a test, we set the log level for a category to TRACE and the method sometimes returns TRACE and sometimes returns DEBUG. Whichever value is returns stays the same until the next time the application is deployed at which point it may change. > The same behavior seems to exist as well on EAP 7.0 and EAP 6.4. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-131) Logger.getEffectiveLevel() not working correctly

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-131?page=com.atlassian.jira.plu... ] Ingo Weiss reassigned JBLOGGING-131: ------------------------------------ Assignee: Ingo Weiss (was: James Perkins) > Logger.getEffectiveLevel() not working correctly > ------------------------------------------------ > > Key: JBLOGGING-131 > URL: https://issues.jboss.org/browse/JBLOGGING-131 > Project: JBoss Logging > Issue Type: Bug > Components: jboss-logging-log4j > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Priority: Minor > > The Logger.getEffectiveLevel() method doesn't seem to return correct values. > In a test, we set the log level for a category to TRACE and the method sometimes returns TRACE and sometimes returns DEBUG. Whichever value is returns stays the same until the next time the application is deployed at which point it may change. > The same behavior seems to exist as well on EAP 7.0 and EAP 6.4. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1676) Call decision FEEL function

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1676?page=com.atlassian.jira.plugi... ] Matteo Mortari edited comment on DROOLS-1676 at 2/19/18 11:15 AM: ------------------------------------------------------------------ A "Caller" model, !screenshot-1.png! where decision "Calling outside" is calling the externalized decision evaluation: !screenshot-2.png! In the normal/good test case, the parametrized serves to call the following "Calling" model: !screenshot-3.png! In this test: https://github.com/kiegroup/drools/blob/eb3cf4946e998718e070a43b307268878... With these two models: https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core/src/t... https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core/src/t... was (Author: tari_manga): A "Caller" model, !screenshot-1.png|thumbnail! where decision "Calling outside" is calling the externalized decision evaluation: !screenshot-2.png|thumbnail! In the normal/good test case, the parametrized serves to call the following "Calling" model: !screenshot-3.png|thumbnail! In this test: https://github.com/kiegroup/drools/blob/eb3cf4946e998718e070a43b307268878... With these two models: https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core/src/t... https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core/src/t... > Call decision FEEL function > --------------------------- > > Key: DROOLS-1676 > URL: https://issues.jboss.org/browse/DROOLS-1676 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Alexandros Koufoudakis > Assignee: Alexandros Koufoudakis > Fix For: 7.4.1.Final > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1676) Call decision FEEL function

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1676?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-1676: ---------------------------------------- A "Caller" model, !screenshot-1.png|thumbnail! where decision "Calling outside" is calling the externalized decision evaluation: !screenshot-2.png|thumbnail! In the normal/good test case, the parametrized serves to call the following "Calling" model: !screenshot-3.png|thumbnail! In this test: https://github.com/kiegroup/drools/blob/eb3cf4946e998718e070a43b307268878... With these two models: https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core/src/t... https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core/src/t... > Call decision FEEL function > --------------------------- > > Key: DROOLS-1676 > URL: https://issues.jboss.org/browse/DROOLS-1676 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Alexandros Koufoudakis > Assignee: Alexandros Koufoudakis > Fix For: 7.4.1.Final > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1676) Call decision FEEL function

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1676?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-1676: ----------------------------------- Attachment: screenshot-3.png > Call decision FEEL function > --------------------------- > > Key: DROOLS-1676 > URL: https://issues.jboss.org/browse/DROOLS-1676 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Alexandros Koufoudakis > Assignee: Alexandros Koufoudakis > Fix For: 7.4.1.Final > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1676) Call decision FEEL function

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1676?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-1676: ----------------------------------- Attachment: screenshot-2.png > Call decision FEEL function > --------------------------- > > Key: DROOLS-1676 > URL: https://issues.jboss.org/browse/DROOLS-1676 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Alexandros Koufoudakis > Assignee: Alexandros Koufoudakis > Fix For: 7.4.1.Final > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1676) Call decision FEEL function

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1676?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-1676: ----------------------------------- Attachment: screenshot-1.png > Call decision FEEL function > --------------------------- > > Key: DROOLS-1676 > URL: https://issues.jboss.org/browse/DROOLS-1676 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Alexandros Koufoudakis > Assignee: Alexandros Koufoudakis > Fix For: 7.4.1.Final > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2339) Improper handling of FileSystemResource on Windows

by Radovan Synek (JIRA)

Radovan Synek created DROOLS-2339: ------------------------------------- Summary: Improper handling of FileSystemResource on Windows Key: DROOLS-2339 URL: https://issues.jboss.org/browse/DROOLS-2339 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.7.0.Final Environment: Windows Reporter: Radovan Synek Assignee: Mario Fusco This issues has been originally reported against OptaPlanner, see the linked issues. PR with a reproducer will follow. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6777) Upgrade to OpenJPA impl compatible with JDK9

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6777?page=com.atlassian.jira.plugin.... ] Scott Marlow closed WFLY-6777. ------------------------------ > Upgrade to OpenJPA impl compatible with JDK9 > -------------------------------------------- > > Key: WFLY-6777 > URL: https://issues.jboss.org/browse/WFLY-6777 > Project: WildFly > Issue Type: Sub-task > Components: JPA / Hibernate > Reporter: Tomaz Cerar > Assignee: Scott Marlow > Priority: Minor > Fix For: 12.0.0.Beta1 > > > OpenJPA tests currently hang our testsuite as serp bytecode enhancer that OpenJPA uses hangs the deployment. > For now test is not run on JDK9, but this should be re-enabled once there is release of openjpa that works fine with jdk9 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6777) Upgrade to OpenJPA impl compatible with JDK9

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6777?page=com.atlassian.jira.plugin.... ] Tomaz Cerar resolved WFLY-6777. ------------------------------- Fix Version/s: 12.0.0.Beta1 Resolution: Done This was fixed some time ago. > Upgrade to OpenJPA impl compatible with JDK9 > -------------------------------------------- > > Key: WFLY-6777 > URL: https://issues.jboss.org/browse/WFLY-6777 > Project: WildFly > Issue Type: Sub-task > Components: JPA / Hibernate > Reporter: Tomaz Cerar > Assignee: Scott Marlow > Priority: Minor > Fix For: 12.0.0.Beta1 > > > OpenJPA tests currently hang our testsuite as serp bytecode enhancer that OpenJPA uses hangs the deployment. > For now test is not run on JDK9, but this should be re-enabled once there is release of openjpa that works fine with jdk9 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 February 2018