September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-67) Improve LogManager formatter capability: System resources, thread ID and minified category

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-67?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on LOGMGR-67: ----------------------------------------------- James Perkins <jperkins(a)redhat.com> changed the Status of [bug 994744|https://bugzilla.redhat.com/show_bug.cgi?id=994744] from ASSIGNED to CLOSED > Improve LogManager formatter capability: System resources, thread ID and minified category > ------------------------------------------------------------------------------------------ > > Key: LOGMGR-67 > URL: https://issues.jboss.org/browse/LOGMGR-67 > Project: JBoss Log Manager > Issue Type: Feature Request > Components: core > Affects Versions: 1.3.2.Final > Environment: JBoss EAP 6.0.1 > Reporter: Jeremy KUHN > Assignee: James Perkins > Labels: jboss > Fix For: 1.5.0.Final, 2.0.0.Beta1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Hello, > We are currently developing a major JEE application running on multiple JBoss EAP 6.0.1 instances in a service oriented architecture. > The current implementation of JBoss-logmanager (1.3.2.Final) shipped with JBoss EAP doesn't provide the functionality we require in term of logging formatting. > We are missing: > - Thread ID (Thread names are too long and of different length that disturb the reading of logs) > - we haven't find a way to get the hostname displayed in the logs, a simple solution would be to be able to include System properties and therefore the jboss.host.name property in the pattern. System properties would also be interesting to identified the log coming from a specific application (we'll have one application deployed per JBoss instance). Ideally, we'd like to have the ability to provide a context name to know which application has logged the event but this seems to have been delivered with logging profiles. > - logback has this interesting feature that lets you minify the log category: instead of org.jboss.logmanager.config.ConfigAction you'll get o.j.l.c.ConfigAction which is more readable in the logs. > Regards -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-110) Property expressions resolved before the PatternFormatter can resolve them

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-110?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-110: ------------------------------------------------ James Perkins <jperkins(a)redhat.com> changed the Status of [bug 994744|https://bugzilla.redhat.com/show_bug.cgi?id=994744] from ASSIGNED to CLOSED > Property expressions resolved before the PatternFormatter can resolve them > -------------------------------------------------------------------------- > > Key: WFCORE-110 > URL: https://issues.jboss.org/browse/WFCORE-110 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > System property expressions defined in {{pattern-formatter}} or {{formatter}} attributes are processed by the {{AttributeDefinition}} rather than left and processed by the {{PatternFormatter}}. This results in invalid pattern values being used and stops the server from logging. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-110) Property expressions resolved before the PatternFormatter can resolve them

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-110?page=com.atlassian.jira.plugin... ] James Perkins moved WFLY-2264 to WFCORE-110: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-110 (was: WFLY-2264) Component/s: Logging (was: Logging) > Property expressions resolved before the PatternFormatter can resolve them > -------------------------------------------------------------------------- > > Key: WFCORE-110 > URL: https://issues.jboss.org/browse/WFCORE-110 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > System property expressions defined in {{pattern-formatter}} or {{formatter}} attributes are processed by the {{AttributeDefinition}} rather than left and processed by the {{PatternFormatter}}. This results in invalid pattern values being used and stops the server from logging. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-109) Update syslog handler attributes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-109?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-109: ------------------------------------------------ James Perkins <jperkins(a)redhat.com> changed the Status of [bug 1011882|https://bugzilla.redhat.com/show_bug.cgi?id=1011882] from NEW to CLOSED > Update syslog handler attributes > -------------------------------- > > Key: WFCORE-109 > URL: https://issues.jboss.org/browse/WFCORE-109 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 1.0.0.Beta1 > > > The syslog handler does not currently expose the formatter for formatting messages. There will also be changes in a future logmanager release for TCP support and various other properties based on the new TCP support. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-109) Update syslog handler attributes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-109?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-109: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1011882 > Update syslog handler attributes > -------------------------------- > > Key: WFCORE-109 > URL: https://issues.jboss.org/browse/WFCORE-109 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 1.0.0.Beta1 > > > The syslog handler does not currently expose the formatter for formatting messages. There will also be changes in a future logmanager release for TCP support and various other properties based on the new TCP support. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-109) Update syslog handler attributes

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-109?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-109: --------------------------------- Fix Version/s: 1.0.0.Beta1 > Update syslog handler attributes > -------------------------------- > > Key: WFCORE-109 > URL: https://issues.jboss.org/browse/WFCORE-109 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 1.0.0.Beta1 > > > The syslog handler does not currently expose the formatter for formatting messages. There will also be changes in a future logmanager release for TCP support and various other properties based on the new TCP support. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-109) Update syslog handler attributes

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-109?page=com.atlassian.jira.plugin... ] James Perkins moved WFLY-1622 to WFCORE-109: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-109 (was: WFLY-1622) Component/s: Logging (was: Logging) > Update syslog handler attributes > -------------------------------- > > Key: WFCORE-109 > URL: https://issues.jboss.org/browse/WFCORE-109 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > The syslog handler does not currently expose the formatter for formatting messages. There will also be changes in a future logmanager release for TCP support and various other properties based on the new TCP support. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-598) accumuate function not working when object chaining is used as accumulate condition

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-598?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-598. -------------------------------- Labels: backport-to-6.0.x (was: ) Fix Version/s: 6.2.0.CR1 Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/dbd530e84 > accumuate function not working when object chaining is used as accumulate condition > ----------------------------------------------------------------------------------- > > Key: DROOLS-598 > URL: https://issues.jboss.org/browse/DROOLS-598 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.Beta2, 6.2.0.CR1, 6.2.0.Final > Reporter: John Le > Assignee: Mario Fusco > Labels: backport-to-6.0.x > Fix For: 6.2.0.CR1 > > Attachments: AccumulateWithPassAndFail.java, SumOfAllIssue.java > > > Please see attached code file to reproduce issue. Rule is supposed to fire and yield 0.0 as the sum but rule does not. If we remove TestA, TestB, TestC and leave only TestD as condition then rule fire. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-598) accumuate function not working when object chaining is used as accumulate condition

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-598?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-598: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > accumuate function not working when object chaining is used as accumulate condition > ----------------------------------------------------------------------------------- > > Key: DROOLS-598 > URL: https://issues.jboss.org/browse/DROOLS-598 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.Beta2, 6.2.0.CR1, 6.2.0.Final > Reporter: John Le > Assignee: Mario Fusco > Attachments: AccumulateWithPassAndFail.java, SumOfAllIssue.java > > > Please see attached code file to reproduce issue. Rule is supposed to fire and yield 0.0 as the sum but rule does not. If we remove TestA, TestB, TestC and leave only TestD as condition then rule fire. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3861) WildFly distribution for CentOS / RHEL via RPM

by Harrison Ripps (JIRA)

Harrison Ripps created WFLY-3861: ------------------------------------ Summary: WildFly distribution for CentOS / RHEL via RPM Key: WFLY-3861 URL: https://issues.jboss.org/browse/WFLY-3861 Project: WildFly Issue Type: Enhancement Components: Server Reporter: Harrison Ripps Assignee: Jason Greene OpenShift Origin would be a great place to showcase the WildFly application runtime. In particular, Origin includes a Java cartridge that could use WildFly as its runtime dependency. However, because WildFly is not distributed in RPM form, it cannot be included in the dependency chain. There have been several discussions on the lack of a Java runtime on the OpenShift mailing lists, most recently: https://lists.openshift.redhat.com/openshift-archives/dev/2014-July/msg00... And a bug has been opened against the OpenShift project as well: https://bugzilla.redhat.com/show_bug.cgi?id=1058581 However, these issues must be resolved upstream and it is our hope that the WildFly community will take this opportunity to become the de facto standard Java application runtime for OpenShift Origin. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2014