April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1923) Discovery: add option to run each discovery requests in a separate thread

by Bela Ban (JIRA)

Bela Ban created JGRP-1923: ------------------------------ Summary: Discovery: add option to run each discovery requests in a separate thread Key: JGRP-1923 URL: https://issues.jboss.org/browse/JGRP-1923 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.6.4 Currently, {{async_discovery}} runs discovery in a separate thread. However, if we try to contact 10 servers and almost all are down and {{sock_conn_timeout}} is high, then discovery might not return any live servers and the caller becomes coordinator. Add attribute {{async_discovery_use_separate_thread_per_request}} to enable this. This is orthogonal to {{async_discovery}}. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4496) Upgrade AESH from 0.33.14 to 0.33.15

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4496?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski commented on WFLY-4496: ------------------------------------------ Upgrade due to: https://issues.jboss.org/browse/WFCORE-608 which should be fixed in AESH not core. > Upgrade AESH from 0.33.14 to 0.33.15 > ------------------------------------ > > Key: WFLY-4496 > URL: https://issues.jboss.org/browse/WFLY-4496 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4496) Upgrade AESH from 0.33.14 to 0.33.15

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4496?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski updated WFLY-4496: ------------------------------------- Issue Type: Component Upgrade (was: Feature Request) > Upgrade AESH from 0.33.14 to 0.33.15 > ------------------------------------ > > Key: WFLY-4496 > URL: https://issues.jboss.org/browse/WFLY-4496 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Bartosz Baranowski > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4496) Upgrade AESH from 0.33.14 to 0.33.15

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4496?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski updated WFLY-4496: ------------------------------------- Priority: Minor (was: Major) > Upgrade AESH from 0.33.14 to 0.33.15 > ------------------------------------ > > Key: WFLY-4496 > URL: https://issues.jboss.org/browse/WFLY-4496 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4496) Upgrade AESH from 0.33.14 to 0.33.15

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created WFLY-4496: ---------------------------------------- Summary: Upgrade AESH from 0.33.14 to 0.33.15 Key: WFLY-4496 URL: https://issues.jboss.org/browse/WFLY-4496 Project: WildFly Issue Type: Feature Request Reporter: Bartosz Baranowski Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4496) Upgrade AESH from 0.33.14 to 0.33.15

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4496?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4496: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1210556 > Upgrade AESH from 0.33.14 to 0.33.15 > ------------------------------------ > > Key: WFLY-4496 > URL: https://issues.jboss.org/browse/WFLY-4496 > Project: WildFly > Issue Type: Feature Request > Reporter: Bartosz Baranowski > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-548) Changing append on a file handler indicates a reload is required when it should be a runtime change

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-548?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-548: --------------------------------- Summary: Changing append on a file handler indicates a reload is required when it should be a runtime change (was: Changing append on a file handler indicates a reload is required when a restart is required) > Changing append on a file handler indicates a reload is required when it should be a runtime change > --------------------------------------------------------------------------------------------------- > > Key: WFCORE-548 > URL: https://issues.jboss.org/browse/WFCORE-548 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > Changing the {{append}} attribute at runtime results in the following output: > {code} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=append,value=false) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {code} > A {{reload}} operation does not stop a file from being appended to. Either the behavior needs to change or the {{process-state}} should be "restart-required". > The issue is likely the file name is checked during boot and hasn't changed therefore the it's not set which would cause the stream to the file to be closed and reopened without the append. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-636) Logging operations should resolve runtime values off the operation

by James Perkins (JIRA)

James Perkins created WFCORE-636: ------------------------------------ Summary: Logging operations should resolve runtime values off the operation Key: WFCORE-636 URL: https://issues.jboss.org/browse/WFCORE-636 Project: WildFly Core Issue Type: Task Components: Logging Reporter: James Perkins Assignee: James Perkins Priority: Minor Some logging operations attempt to resolve runtime values from the operation where the updated model from the {{MODEL}} stage should be used. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-633) Erroneous name attribute on root-logger after add-handler operation

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-633?page=com.atlassian.jira.plugin... ] James Perkins resolved WFCORE-633. ---------------------------------- Resolution: Won't Fix See the comments on https://bugzilla.redhat.com/show_bug.cgi?id=1017881#c12 for the reason this won't be fixed. > Erroneous name attribute on root-logger after add-handler operation > -------------------------------------------------------------------- > > Key: WFCORE-633 > URL: https://issues.jboss.org/browse/WFCORE-633 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > Execution of the {{add-handler}} operation adds a name attribute with the handlers name to the root-logger model. > {code} > "root-logger" => {"ROOT" => { > "filter" => undefined, > "filter-spec" => undefined, > "handlers" => [ > "FILE", > "CONSOLE" > ], > "level" => "INFO", > "name" => "CONSOLE" > }} > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-635) Require placeholder resources for non-proxy runtime resources

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-635: --------------------------------------- Summary: Require placeholder resources for non-proxy runtime resources Key: WFCORE-635 URL: https://issues.jboss.org/browse/WFCORE-635 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 1.0.0.CR1 ReadResourceHandler has a nullSafeReadResource method that returns a PlaceholderResource for any address whose MRR says it's runtime: https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/j... That basically allows devs to not bother creating runtime resources, but breaks things where there's an assumption that no resource object will be present when no actual resource exists. See discussion at https://github.com/wildfly/wildfly/pull/6607 This JIRA is to get rid of that behavior, restricting it to, at most, proxy resource cases. See also WFCORE-580 which is a similar problem. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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