October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBLOGGING-85) slf4j-jboss-logmanager does not support parametization of a logging statement in the presence of a Throwable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-85?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on JBLOGGING-85: -------------------------------------------------- Ondrej Lukas <olukas(a)redhat.com> changed the Status of [bug 876489|https://bugzilla.redhat.com/show_bug.cgi?id=876489] from ON_QA to VERIFIED > slf4j-jboss-logmanager does not support parametization of a logging statement in the presence of a Throwable > ------------------------------------------------------------------------------------------------------------ > > Key: JBLOGGING-85 > URL: https://issues.jboss.org/browse/JBLOGGING-85 > Project: JBoss Logging > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: slf4j-jboss-logmanager > Reporter: Hercules Zeus > Assignee: James Perkins > > http://www.slf4j.org/faq.html#paramException describes that from slf4j 1.6 onwards doing the following will print a stacktrace: > logger.error("Failed to format {}", s, e); > However, due to the implementation of org.slf4j.impl.MessageFormatter in slf4j-jboss-logmanager, when logger.error(String, Object, Object) is called, even if the third parameter is a Throwable, it is not recognised as such. > Investigating further, it seems that org.slf4j.impl.MessageFormatter is probably just an old copy of org.slf4j.helpers.MessageFormatter in slfj-api 1.6.1, where most formatting methods used to return a String now returns a FormattingTuple. > This issue can be fixed by making all calls in Slf4Logger to org.slf4j.impl.MessageFormatter to call org.slf4j.helpers.MessageFormatter instead and appropriately call ExtLogRecord.setThrown(formattingTuple.getThrowable()). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-85) slf4j-jboss-logmanager does not support parametization of a logging statement in the presence of a Throwable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-85?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on JBLOGGING-85: -------------------------------------------------- Ondrej Lukas <olukas(a)redhat.com> made a comment on [bug 876489|https://bugzilla.redhat.com/show_bug.cgi?id=876489] Verified on EAP 6.2.0.ER4 > slf4j-jboss-logmanager does not support parametization of a logging statement in the presence of a Throwable > ------------------------------------------------------------------------------------------------------------ > > Key: JBLOGGING-85 > URL: https://issues.jboss.org/browse/JBLOGGING-85 > Project: JBoss Logging > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: slf4j-jboss-logmanager > Reporter: Hercules Zeus > Assignee: James Perkins > > http://www.slf4j.org/faq.html#paramException describes that from slf4j 1.6 onwards doing the following will print a stacktrace: > logger.error("Failed to format {}", s, e); > However, due to the implementation of org.slf4j.impl.MessageFormatter in slf4j-jboss-logmanager, when logger.error(String, Object, Object) is called, even if the third parameter is a Throwable, it is not recognised as such. > Investigating further, it seems that org.slf4j.impl.MessageFormatter is probably just an old copy of org.slf4j.helpers.MessageFormatter in slfj-api 1.6.1, where most formatting methods used to return a String now returns a FormattingTuple. > This issue can be fixed by making all calls in Slf4Logger to org.slf4j.impl.MessageFormatter to call org.slf4j.helpers.MessageFormatter instead and appropriately call ExtLogRecord.setThrown(formattingTuple.getThrowable()). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1358) Support Windows paths with spaces in batch files

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1358?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1358: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 916960|https://bugzilla.redhat.com/show_bug.cgi?id=916960] from NEW to VERIFIED > Support Windows paths with spaces in batch files > ------------------------------------------------ > > Key: WFLY-1358 > URL: https://issues.jboss.org/browse/WFLY-1358 > Project: WildFly > Issue Type: Enhancement > Components: Scripts > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > If a Windows path has a space or {{()}} in it the scripts fail to execute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1358) Support Windows paths with spaces in batch files

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1358?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1358: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> made a comment on [bug 916960|https://bugzilla.redhat.com/show_bug.cgi?id=916960] I retested this with latest EAP build and the issue is fixed. Verified on EAP 6.2.0.ER5. > Support Windows paths with spaces in batch files > ------------------------------------------------ > > Key: WFLY-1358 > URL: https://issues.jboss.org/browse/WFLY-1358 > Project: WildFly > Issue Type: Enhancement > Components: Scripts > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > If a Windows path has a space or {{()}} in it the scripts fail to execute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-291) ClassCastException during constraint jitting when an interface is used for implementation and traiting

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-291?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-291: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > ClassCastException during constraint jitting when an interface is used for implementation and traiting > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-291 > URL: https://issues.jboss.org/browse/DROOLS-291 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR4 > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > > The following combination is needed: > - an interface IX with at least one getter/setter pair > - a trait IY extending IX > - a class K implementing IX > - a jittable constraint on IX > The constraint is first triggered by an "instance" of IY, > but jitted by an instance of K. > The condition analyzer assumes that IY is the natural > domain of the constratint, rather than IX. The jitted > constraint will then try to cast K to IY, resulting in > a disruptive CCE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2255) ManagedAuditLoggerImpl doesn't replace handlers correctly

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2255?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2255: ----------------------------- Component/s: Domain Management (was: Logging) > ManagedAuditLoggerImpl doesn't replace handlers correctly > --------------------------------------------------------- > > Key: WFLY-2255 > URL: https://issues.jboss.org/browse/WFLY-2255 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Josef Cacek > Assignee: Josef Cacek > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2172) Resurrect the mixed domain testing and fix any problems

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2172?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2172: ----------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> made a comment on [bug 1015243|https://bugzilla.redhat.com/show_bug.cgi?id=1015243] Brian, Kabir, thank you for comments. Changing qa_ack to +. There is no description and BZ title implied that it would be QA task. > Resurrect the mixed domain testing and fix any problems > ------------------------------------------------------- > > Key: WFLY-2172 > URL: https://issues.jboss.org/browse/WFLY-2172 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 8.0.0.CR1 > > > THis has not been run for quite some time, and needs to be included in the general testing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2256) Add a TRACE level category for the operations used to start a server.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-2256: -------------------------------------- Summary: Add a TRACE level category for the operations used to start a server. Key: WFLY-2256 URL: https://issues.jboss.org/browse/WFLY-2256 Project: WildFly Issue Type: Enhancement Components: Domain Management, Logging Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 8.0.0.CR1 Sometimes after being able to start a server from the XML configuration it is useful to be able to identify the actual operations that are executed to start the server. >From a development perspective this is useful for double checking the operations are as we expect. >From an end user perspective this can be useful to identify the set of equivalent operations needed if the same was to be achieved in a CLI script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2172) Resurrect the mixed domain testing and fix any problems

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2172?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2172: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> made a comment on [bug 1015243|https://bugzilla.redhat.com/show_bug.cgi?id=1015243] The work has already been done. It lives here: https://github.com/jbossas/jboss-eap/pull/510. > Resurrect the mixed domain testing and fix any problems > ------------------------------------------------------- > > Key: WFLY-2172 > URL: https://issues.jboss.org/browse/WFLY-2172 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 8.0.0.CR1 > > > THis has not been run for quite some time, and needs to be included in the general testing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2104) Patch-gen tool should provide users with better error messages

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/WFLY-2104?page=com.atlassian.jira.plugin.... ] Emanuel Muckenhuber resolved WFLY-2104. --------------------------------------- Fix Version/s: 8.0.0.CR1 Resolution: Done > Patch-gen tool should provide users with better error messages > -------------------------------------------------------------- > > Key: WFLY-2104 > URL: https://issues.jboss.org/browse/WFLY-2104 > Project: WildFly > Issue Type: Feature Request > Components: Patching > Reporter: Vaclav Tunka > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.CR1 > > > Patch-gen tool should provide better error messages to user. Eg. telling what exactly is wrong, instead of listing the full usage. > [vtunka@voidray tool]$ ./tool.sh --create-template --cumlative 6.2.0 > USAGE: > patch-gen.sh --create-template --one-of [patch-id] > patch-gen.sh --create-template --cumulative [patch-id] > this will create a patch-config-[patch-id].xml > if this is not desired just append --std.out > There is a typo in --cumlative instead of --cumulative, but the tool doesn't say that, and user is left to explore possible sources of error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 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 2013