April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4564) Switch to version 4 of the management schema

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-4564: -------------------------------------- Summary: Switch to version 4 of the management schema Key: WFLY-4564 URL: https://issues.jboss.org/browse/WFLY-4564 Project: WildFly Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: No Release -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4563) Review log categories and remove/change where necessary

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4563?page=com.atlassian.jira.plugin.... ] James Perkins moved WFCORE-667 to WFLY-4563: -------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-4563 (was: WFCORE-667) Component/s: Logging (was: Logging) Fix Version/s: (was: 1.0.0.CR1) > Review log categories and remove/change where necessary > ------------------------------------------------------- > > Key: WFLY-4563 > URL: https://issues.jboss.org/browse/WFLY-4563 > Project: WildFly > Issue Type: Task > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > Look for situations like; > {code} > MessagingLogger ROOT_LOGGER = Logger.getMessageLogger(MessagingLogger.class, "org.jboss.as.messaging"); > MessagingLogger MESSAGING_LOGGER = Logger.getMessageLogger(MessagingLogger.class, "org.jboss.messaging"); > {code} > Possibly change all to org.wildfly.*. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-667) Review log categories and remove/change where necessary

by James Perkins (JIRA)

James Perkins created WFCORE-667: ------------------------------------ Summary: Review log categories and remove/change where necessary Key: WFCORE-667 URL: https://issues.jboss.org/browse/WFCORE-667 Project: WildFly Core Issue Type: Task Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 1.0.0.CR1 Look for situations like; {code} MessagingLogger ROOT_LOGGER = Logger.getMessageLogger(MessagingLogger.class, "org.jboss.as.messaging"); MessagingLogger MESSAGING_LOGGER = Logger.getMessageLogger(MessagingLogger.class, "org.jboss.messaging"); {code} Possibly change all to org.wildfly.*. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-666) Log file validation should check if a path is absolute if a relative-to is defined

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-666?page=com.atlassian.jira.plugin... ] James Perkins moved WFLY-4545 to WFCORE-666: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-666 (was: WFLY-4545) Component/s: Logging (was: Logging) > Log file validation should check if a path is absolute if a relative-to is defined > ---------------------------------------------------------------------------------- > > Key: WFCORE-666 > URL: https://issues.jboss.org/browse/WFCORE-666 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > The {{path}} attribute on a file should be validated to not be absolute if a {{relative-to}} attribute was also defined. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-637) /subsystem=logging/log-file resource cannot cope with an expression in the path

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-637?page=com.atlassian.jira.plugin... ] James Perkins commented on WFCORE-637: -------------------------------------- I'm changing this to an optional enhancement. We already have a limitation that the file-handlers must be in the {{jboss.server.log.dir}} directory. Having a limitation of not being able to resolve expressions in the path name seems okay to me. I can understand the use-case where a user would like to use an expression for the path. The issue is there's no good way to dynamically resolve an expression in a resource. This would lead to some sort of collection which stores the resolved path names. Which could only be done in the {{RUNTIME}} stage and would lead to files not being able to be listed or read in the something like admin-only mode. For now we just need to keep things as they are and consider an enhancement to this limitation in the future. > /subsystem=logging/log-file resource cannot cope with an expression in the path > ------------------------------------------------------------------------------- > > Key: WFCORE-637 > URL: https://issues.jboss.org/browse/WFCORE-637 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Affects Versions: 1.0.0.Beta3 > Reporter: Ivo Studensky > Assignee: James Perkins > Priority: Optional > > In log subsystem, nested expression can be used for path. > {noformat} > "path" => { > "type" => STRING, > "description" => "The filesystem path.", > "expressions-allowed" => true, > "nillable" => false, > "min-length" => 1L, > "max-length" => 2147483647L > } > {noformat} > so if I use following log configuration : > {noformat} > <periodic-rotating-file-handler name="FILE" autoflush="true"> > <formatter> > <named-formatter name="PATTERN"/> > </formatter> > <file relative-to="jboss.server.log.dir" path="${jboss.server.name}.log"/> > <suffix value=".yyyy-MM-dd"/> > <append value="true"/> > {noformat} > server log name will be HOST_NAME.log and there is no problems to write. > However, there is no log-file resource for it. This also leads into an issue that it cannot be displayed in Admin console Log Viewer menu. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-637) /subsystem=logging/log-file resource cannot cope with an expression in the path

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-637?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-637: --------------------------------- Priority: Optional (was: Major) > /subsystem=logging/log-file resource cannot cope with an expression in the path > ------------------------------------------------------------------------------- > > Key: WFCORE-637 > URL: https://issues.jboss.org/browse/WFCORE-637 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Affects Versions: 1.0.0.Beta3 > Reporter: Ivo Studensky > Assignee: James Perkins > Priority: Optional > > In log subsystem, nested expression can be used for path. > {noformat} > "path" => { > "type" => STRING, > "description" => "The filesystem path.", > "expressions-allowed" => true, > "nillable" => false, > "min-length" => 1L, > "max-length" => 2147483647L > } > {noformat} > so if I use following log configuration : > {noformat} > <periodic-rotating-file-handler name="FILE" autoflush="true"> > <formatter> > <named-formatter name="PATTERN"/> > </formatter> > <file relative-to="jboss.server.log.dir" path="${jboss.server.name}.log"/> > <suffix value=".yyyy-MM-dd"/> > <append value="true"/> > {noformat} > server log name will be HOST_NAME.log and there is no problems to write. > However, there is no log-file resource for it. This also leads into an issue that it cannot be displayed in Admin console Log Viewer menu. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-637) /subsystem=logging/log-file resource cannot cope with an expression in the path

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-637?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-637: --------------------------------- Issue Type: Enhancement (was: Bug) > /subsystem=logging/log-file resource cannot cope with an expression in the path > ------------------------------------------------------------------------------- > > Key: WFCORE-637 > URL: https://issues.jboss.org/browse/WFCORE-637 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Affects Versions: 1.0.0.Beta3 > Reporter: Ivo Studensky > Assignee: James Perkins > > In log subsystem, nested expression can be used for path. > {noformat} > "path" => { > "type" => STRING, > "description" => "The filesystem path.", > "expressions-allowed" => true, > "nillable" => false, > "min-length" => 1L, > "max-length" => 2147483647L > } > {noformat} > so if I use following log configuration : > {noformat} > <periodic-rotating-file-handler name="FILE" autoflush="true"> > <formatter> > <named-formatter name="PATTERN"/> > </formatter> > <file relative-to="jboss.server.log.dir" path="${jboss.server.name}.log"/> > <suffix value=".yyyy-MM-dd"/> > <append value="true"/> > {noformat} > server log name will be HOST_NAME.log and there is no problems to write. > However, there is no log-file resource for it. This also leads into an issue that it cannot be displayed in Admin console Log Viewer menu. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1752) Concurrent message headers modification causes that message is never sent

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1752?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JGRP-1752: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1043853, https://bugzilla.redhat.com/show_bug.cgi?id=1215786 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1043853) > Concurrent message headers modification causes that message is never sent > ------------------------------------------------------------------------- > > Key: JGRP-1752 > URL: https://issues.jboss.org/browse/JGRP-1752 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.1 > Reporter: Radim Vansa > Assignee: Bela Ban > Labels: 621 > Fix For: 3.4.2, 3.5 > > > Under some circumstances the TP protocol may try to add the TP header to message twice concurrently. > This happens for example when the stable message triggers retransmission while the message has been sent right now. > This may result in ArrayOutOfBoundException in Headers._putHeader and/or subsequent NullPointerException in Headers.size(). The retransmission attempt always fails, the message is never delivered. Moreover, keeping this (and possibly following) messages in the transmission table can lead to OOME. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-637) /subsystem=logging/log-file resource cannot cope with an expression in the path

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-637?page=com.atlassian.jira.plugin... ] James Perkins reassigned WFCORE-637: ------------------------------------ Assignee: James Perkins (was: Ivo Studensky) > /subsystem=logging/log-file resource cannot cope with an expression in the path > ------------------------------------------------------------------------------- > > Key: WFCORE-637 > URL: https://issues.jboss.org/browse/WFCORE-637 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Affects Versions: 1.0.0.Beta3 > Reporter: Ivo Studensky > Assignee: James Perkins > > In log subsystem, nested expression can be used for path. > {noformat} > "path" => { > "type" => STRING, > "description" => "The filesystem path.", > "expressions-allowed" => true, > "nillable" => false, > "min-length" => 1L, > "max-length" => 2147483647L > } > {noformat} > so if I use following log configuration : > {noformat} > <periodic-rotating-file-handler name="FILE" autoflush="true"> > <formatter> > <named-formatter name="PATTERN"/> > </formatter> > <file relative-to="jboss.server.log.dir" path="${jboss.server.name}.log"/> > <suffix value=".yyyy-MM-dd"/> > <append value="true"/> > {noformat} > server log name will be HOST_NAME.log and there is no problems to write. > However, there is no log-file resource for it. This also leads into an issue that it cannot be displayed in Admin console Log Viewer menu. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1260) Allow System Property to override default First In First Out (FIFO) pooling behavior

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1260?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1260. ------------------------------------ Assignee: Johnathon Lee (was: Jesper Pedersen) Fix Version/s: 1.0.32.Final Resolution: Done > Allow System Property to override default First In First Out (FIFO) pooling behavior > ------------------------------------------------------------------------------------ > > Key: JBJCA-1260 > URL: https://issues.jboss.org/browse/JBJCA-1260 > Project: IronJacamar > Issue Type: Support Patch > Components: Core > Affects Versions: 1.0.32.Final > Reporter: Johnathon Lee > Assignee: Johnathon Lee > Fix For: 1.0.32.Final > > > Introduce a system property "filo-pool-behavior" to override (revert) the changes introduced by JBJCA-1005. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 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 April 2015