April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1785) Release WildFly Elytron 1.9.0.CR3

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1785: ------------------------------------- Summary: Release WildFly Elytron 1.9.0.CR3 Key: ELY-1785 URL: https://issues.jboss.org/browse/ELY-1785 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.9.0.CR3 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11984) ChannelCommandDispatcherFactory does not notify any GroupListener

by Gab And (Jira)

[ https://issues.jboss.org/browse/WFLY-11984?page=com.atlassian.jira.plugin... ] Gab And commented on WFLY-11984: -------------------------------- Glad to help. I've checked the code for 15.0.1.Final and it has the same issue. And it may be also in lower versions. > ChannelCommandDispatcherFactory does not notify any GroupListener > ----------------------------------------------------------------- > > Key: WFLY-11984 > URL: https://issues.jboss.org/browse/WFLY-11984 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 16.0.0.Final > Reporter: Gab And > Assignee: Paul Ferraro > Priority: Blocker > > checkout ChannelCommandDispatcherFactory > line 267 > if (this.listeners.isEmpty()) {...} > There should be a negation which should look like !this.listeners.isEmpty() -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11982) HAL-1576 - Add BusyWorkerThreadCount metric under IO Worker Runtime view in the management console

by Harald Pehl (Jira)

[ https://issues.jboss.org/browse/WFLY-11982?page=com.atlassian.jira.plugin... ] Harald Pehl closed WFLY-11982. ------------------------------ Resolution: Won't Fix Ok, now I get it. Though I don't know if we really need a back-port for WF 16. AFAIK back-ports are only done for EAP. I think we can close this one. > HAL-1576 - Add BusyWorkerThreadCount metric under IO Worker Runtime view in the management console > -------------------------------------------------------------------------------------------------- > > Key: WFLY-11982 > URL: https://issues.jboss.org/browse/WFLY-11982 > Project: WildFly > Issue Type: Enhancement > Components: Web Console > Affects Versions: 16.0.0.Final > Reporter: Masafumi Miura > Assignee: Harald Pehl > Priority: Major > > WFCORE-3333 exposed a number of busy threads in the task worker thread pool in JBoss CLI. Add the metric under IO Worker Runtime in the management console. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11982) HAL-1576 - Add BusyWorkerThreadCount metric under IO Worker Runtime view in the management console

by Harald Pehl (Jira)

[ https://issues.jboss.org/browse/WFLY-11982?page=com.atlassian.jira.plugin... ] Harald Pehl updated WFLY-11982: ------------------------------- Git Pull Request: https://github.com/hal/console/pull/307 (was: https://github.com/hal/console/pull/306, https://github.com/hal/console/pull/307, https://github.com/hal/console/pull/308) > HAL-1576 - Add BusyWorkerThreadCount metric under IO Worker Runtime view in the management console > -------------------------------------------------------------------------------------------------- > > Key: WFLY-11982 > URL: https://issues.jboss.org/browse/WFLY-11982 > Project: WildFly > Issue Type: Enhancement > Components: Web Console > Affects Versions: 16.0.0.Final > Reporter: Masafumi Miura > Assignee: Harald Pehl > Priority: Major > > WFCORE-3333 exposed a number of busy threads in the task worker thread pool in JBoss CLI. Add the metric under IO Worker Runtime in the management console. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11983) Unify line-endings of bat scripts (regression against WF15)

by Marek Kopecky (Jira)

[ https://issues.jboss.org/browse/WFLY-11983?page=com.atlassian.jira.plugin... ] Marek Kopecky updated WFLY-11983: --------------------------------- Affects Version/s: 16.0.0.Final > Unify line-endings of bat scripts (regression against WF15) > ----------------------------------------------------------- > > Key: WFLY-11983 > URL: https://issues.jboss.org/browse/WFLY-11983 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 16.0.0.Final > Reporter: Marek Kopecky > Assignee: James Perkins > Priority: Critical > > Line-endings of bat scripts should be unified. This is regression against WF15. > Some files in WF16 uses CRLF, another LF only. We need to clarify the recommended line ending and use this line ending in all Windows scripts. > WF16: > {noformat} > $ find | grep bat$ | xargs file > ./wsprovide.bat: DOS batch file, ASCII text, with CRLF line terminators > ./jboss-cli.bat: DOS batch file, ASCII text > ./elytron-tool.bat: DOS batch file, ASCII text > ./domain.bat: DOS batch file, ASCII text, with CRLF line terminators > ./wsconsume.bat: DOS batch file, ASCII text, with CRLF line terminators > ./standalone.bat: DOS batch file, ASCII text, with CRLF line terminators > ./vault.bat: DOS batch file, ASCII text, with CRLF line terminators > ./domain.conf.bat: ASCII text, with CRLF line terminators > ./common.bat: DOS batch file, ASCII text, with CRLF line terminators > ./jdr.bat: DOS batch file, ASCII text > ./jconsole.bat: DOS batch file, ASCII text > ./appclient.bat: DOS batch file, ASCII text, with CRLF line terminators > ./appclient.conf.bat: ASCII text, with CRLF line terminators > ./standalone.conf.bat: ASCII text, with CRLF line terminators > ./add-user.bat: DOS batch file, ASCII text > $ > {noformat} > WF15: > {noformat} > $ find | grep bat$ | xargs file > ./wsprovide.bat: DOS batch file, ASCII text, with CRLF line terminators > ./jboss-cli.bat: DOS batch file, ASCII text, with CRLF line terminators > ./elytron-tool.bat: DOS batch file, ASCII text, with CRLF line terminators > ./domain.bat: DOS batch file, ASCII text, with CRLF line terminators > ./wsconsume.bat: DOS batch file, ASCII text, with CRLF line terminators > ./standalone.bat: DOS batch file, ASCII text, with CRLF line terminators > ./vault.bat: DOS batch file, ASCII text, with CRLF line terminators > ./domain.conf.bat: ASCII text, with CRLF line terminators > ./common.bat: DOS batch file, ASCII text, with CRLF line terminators > ./jdr.bat: DOS batch file, ASCII text, with CRLF line terminators > ./jconsole.bat: DOS batch file, ASCII text, with CRLF line terminators > ./appclient.bat: DOS batch file, ASCII text, with CRLF line terminators > ./appclient.conf.bat: ASCII text, with CRLF line terminators > ./standalone.conf.bat: ASCII text, with CRLF line terminators > ./add-user.bat: DOS batch file, ASCII text, with CRLF line terminators > $ > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6944) Encode session affinity using multiple routes, if supported by the load balancer

by Harald Pehl (Jira)

[ https://issues.jboss.org/browse/WFLY-6944?page=com.atlassian.jira.plugin.... ] Harald Pehl commented on WFLY-6944: ----------------------------------- I'm planing the console payload for WF 17. [~pferraro] will this be part of WF 17? > Encode session affinity using multiple routes, if supported by the load balancer > -------------------------------------------------------------------------------- > > Key: WFLY-6944 > URL: https://issues.jboss.org/browse/WFLY-6944 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Currently, session affinity is specified as a single route, usually the primary owner of a session. However, if this node is not active (from the load balancer's perspective), then the load balancer will select another node of its choosing. This is less than ideal, since some nodes are more optimal than others. Better is to expression session affinity as an ordered list of nodes. The load balancer can then choose the 1st node in the list that is active, and cascade on failures accordingly. From the server's perspective, the affinity list should have the following order: > 1. The primary owner > 2. Any backup owners > 3. The local node (if the local node is not an owner) > There are a couple of ways a load balancer can indicate that it supports multiple routes. > 1. Static configuration, e.g. routing="NONE|OWNER|LOCAL|RANKED" > 2. Adding an HTTP header to a proxied request, which can be detected by the server handling the request > #1 has the advantage of simplicity - but requires that users manually apply this configuration to gain optimal performance. This would also let us allow users (for even the single node affinity case) to toggle between local affinity or primary owner affinity, or even no routing. > #2 has the advantage of applying this optimization automatically, but incurs the cost of an additional header to every request -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11982) HAL-1576 - Add BusyWorkerThreadCount metric under IO Worker Runtime view in the management console

by Masafumi Miura (Jira)

[ https://issues.jboss.org/browse/WFLY-11982?page=com.atlassian.jira.plugin... ] Masafumi Miura commented on WFLY-11982: --------------------------------------- If I understand correctly, the latest WildFly 16 comes with hal-console 3.1. and EAP 7.2.x comes with hal-console 3.0.x. So, I thought that both WFLY and JBEAP JIRAs needs to be created in order to track and merge the PR for each branch. Please correct me if I'm wrong and please close this WFLY JIRA if it's not necessary. > HAL-1576 - Add BusyWorkerThreadCount metric under IO Worker Runtime view in the management console > -------------------------------------------------------------------------------------------------- > > Key: WFLY-11982 > URL: https://issues.jboss.org/browse/WFLY-11982 > Project: WildFly > Issue Type: Enhancement > Components: Web Console > Affects Versions: 16.0.0.Final > Reporter: Masafumi Miura > Assignee: Harald Pehl > Priority: Major > > WFCORE-3333 exposed a number of busy threads in the task worker thread pool in JBoss CLI. Add the metric under IO Worker Runtime in the management console. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11984) ChannelCommandDispatcherFactory does not notify any GroupListener

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-11984?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-11984: ------------------------------------- How sloppy of me. Thanks for the report. > ChannelCommandDispatcherFactory does not notify any GroupListener > ----------------------------------------------------------------- > > Key: WFLY-11984 > URL: https://issues.jboss.org/browse/WFLY-11984 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 16.0.0.Final > Reporter: Gab And > Assignee: Paul Ferraro > Priority: Blocker > > checkout ChannelCommandDispatcherFactory > line 267 > if (this.listeners.isEmpty()) {...} > There should be a negation which should look like !this.listeners.isEmpty() -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11984) ChannelCommandDispatcherFactory does not notify any GroupListener

by Gab And (Jira)

Gab And created WFLY-11984: ------------------------------ Summary: ChannelCommandDispatcherFactory does not notify any GroupListener Key: WFLY-11984 URL: https://issues.jboss.org/browse/WFLY-11984 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 16.0.0.Final Reporter: Gab And Assignee: Paul Ferraro checkout ChannelCommandDispatcherFactory line 267 if (this.listeners.isEmpty()) {...} There should be a negation which should look like !this.listeners.isEmpty() -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11982) HAL-1576 - Add BusyWorkerThreadCount metric under IO Worker Runtime view in the management console

by Harald Pehl (Jira)

[ https://issues.jboss.org/browse/WFLY-11982?page=com.atlassian.jira.plugin... ] Harald Pehl commented on WFLY-11982: ------------------------------------ [~mmiura] Not quite sure what this issue is for? > HAL-1576 - Add BusyWorkerThreadCount metric under IO Worker Runtime view in the management console > -------------------------------------------------------------------------------------------------- > > Key: WFLY-11982 > URL: https://issues.jboss.org/browse/WFLY-11982 > Project: WildFly > Issue Type: Enhancement > Components: Web Console > Affects Versions: 16.0.0.Final > Reporter: Masafumi Miura > Assignee: Harald Pehl > Priority: Major > > WFCORE-3333 exposed a number of busy threads in the task worker thread pool in JBoss CLI. Add the metric under IO Worker Runtime in the management console. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 2019