June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (REMJMX-150) Release Remoting JMX 3.0.0.CR1

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-150: --------------------------------------- Summary: Release Remoting JMX 3.0.0.CR1 Key: REMJMX-150 URL: https://issues.jboss.org/browse/REMJMX-150 Project: Remoting JMX Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.CR1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-149) Bring remaining component dependencies in-line with WildFly Core

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-149: --------------------------------------- Summary: Bring remaining component dependencies in-line with WildFly Core Key: REMJMX-149 URL: https://issues.jboss.org/browse/REMJMX-149 Project: Remoting JMX Issue Type: Component Upgrade Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.CR1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-148) Upgrade JBoss Remoting to 5.0.0.CR2

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-148: --------------------------------------- Summary: Upgrade JBoss Remoting to 5.0.0.CR2 Key: REMJMX-148 URL: https://issues.jboss.org/browse/REMJMX-148 Project: Remoting JMX Issue Type: Component Upgrade Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.CR1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-147) Upgrade WildFly Elytron to 1.1.0.CR1

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-147: --------------------------------------- Summary: Upgrade WildFly Elytron to 1.1.0.CR1 Key: REMJMX-147 URL: https://issues.jboss.org/browse/REMJMX-147 Project: Remoting JMX Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.CR1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3032) Upgrade to Elytron tool 1.0.0.CR1

by Peter Skopek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3032?page=com.atlassian.jira.plugi... ] Peter Skopek moved JBEAP-11873 to WFCORE-3032: ---------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3032 (was: JBEAP-11873) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) > Upgrade to Elytron tool 1.0.0.CR1 > --------------------------------- > > Key: WFCORE-3032 > URL: https://issues.jboss.org/browse/WFCORE-3032 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Peter Skopek > Assignee: Peter Skopek > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9027) mod_cluster stop/stop-context operation results do not inform whether session draining was successful

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-9027: ------------------------------------ Summary: mod_cluster stop/stop-context operation results do not inform whether session draining was successful Key: WFLY-9027 URL: https://issues.jboss.org/browse/WFLY-9027 Project: WildFly Issue Type: Bug Components: mod_cluster Affects Versions: 11.0.0.Alpha1 Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 11.0.0.Beta1 [4:20 PM] Radoslav Husar: Also, the mgmt operation result doesn't provide the resulting status of stopping, i.e. if draining was complete [4:20 PM] Radoslav Husar: [4:20 PM] Radoslav Husar: [standalone@localhost:9990 /] /subsystem=modcluster:stop(waittime=10 {"outcome" => "success"} [4:21 PM] Radoslav Husar: 16:19:20,809 INFO [org.jboss.modcluster] (management-handler-thread - 3) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/clusterbench in 10 seconds. 16:19:30,814 WARN [org.jboss.modcluster] (management-handler-thread - 3) MODCLUSTER000025: Failed to drain 1 remaining active sessions from default-host:/clusterbench within 10.0 seconds -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9026) mod_cluster stop/stop-context operation results do not inform whether session draining was successful

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9026?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9026: --------------------------------- Description: [4:20 PM] Radoslav Husar: Also, the mgmt operation result doesn't provide the resulting status of stopping, i.e. if draining was complete [4:20 PM] Radoslav Husar: [4:20 PM] Radoslav Husar: [standalone@localhost:9990 /] /subsystem=modcluster:stop(waittime=10 {"outcome" => "success"} [4:21 PM] Radoslav Husar: 16:19:20,809 INFO [org.jboss.modcluster] (management-handler-thread - 3) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/clusterbench in 10 seconds. 16:19:30,814 WARN [org.jboss.modcluster] (management-handler-thread - 3) MODCLUSTER000025: Failed to drain 1 remaining active sessions from default-host:/clusterbench within 10.0 seconds was: [4:20 PM] Radoslav Husar: [standalone@localhost:9990 /] /subsystem=modcluster:stop(waittime=10 {"outcome" => "success"} [4:21 PM] Radoslav Husar: 16:19:20,809 INFO [org.jboss.modcluster] (management-handler-thread - 3) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/clusterbench in 10 seconds. 16:19:30,814 WARN [org.jboss.modcluster] (management-handler-thread - 3) MODCLUSTER000025: Failed to drain 1 remaining active sessions from default-host:/clusterbench within 10.0 seconds > mod_cluster stop/stop-context operation results do not inform whether session draining was successful > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-9026 > URL: https://issues.jboss.org/browse/WFLY-9026 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 11.0.0.Beta1 > > > [4:20 PM] Radoslav Husar: Also, the mgmt operation result doesn't provide the resulting status of stopping, i.e. if draining was complete > [4:20 PM] Radoslav Husar: > [4:20 PM] Radoslav Husar: > [standalone@localhost:9990 /] /subsystem=modcluster:stop(waittime=10 > {"outcome" => "success"} > [4:21 PM] Radoslav Husar: > 16:19:20,809 INFO [org.jboss.modcluster] (management-handler-thread - 3) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/clusterbench in 10 seconds. > 16:19:30,814 WARN [org.jboss.modcluster] (management-handler-thread - 3) MODCLUSTER000025: Failed to drain 1 remaining active sessions from default-host:/clusterbench within 10.0 seconds -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9026) mod_cluster stop/stop-context operation results do not inform whether session draining was successful

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-9026: ------------------------------------ Summary: mod_cluster stop/stop-context operation results do not inform whether session draining was successful Key: WFLY-9026 URL: https://issues.jboss.org/browse/WFLY-9026 Project: WildFly Issue Type: Component Upgrade Components: mod_cluster Affects Versions: 11.0.0.Alpha1 Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 11.0.0.Beta1 [4:20 PM] Radoslav Husar: [standalone@localhost:9990 /] /subsystem=modcluster:stop(waittime=10 {"outcome" => "success"} [4:21 PM] Radoslav Husar: 16:19:20,809 INFO [org.jboss.modcluster] (management-handler-thread - 3) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/clusterbench in 10 seconds. 16:19:30,814 WARN [org.jboss.modcluster] (management-handler-thread - 3) MODCLUSTER000025: Failed to drain 1 remaining active sessions from default-host:/clusterbench within 10.0 seconds -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9026) mod_cluster stop/stop-context operation results do not inform whether session draining was successful

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9026?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9026: --------------------------------- Issue Type: Bug (was: Component Upgrade) > mod_cluster stop/stop-context operation results do not inform whether session draining was successful > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-9026 > URL: https://issues.jboss.org/browse/WFLY-9026 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 11.0.0.Beta1 > > > [4:20 PM] Radoslav Husar: > [standalone@localhost:9990 /] /subsystem=modcluster:stop(waittime=10 > {"outcome" => "success"} > [4:21 PM] Radoslav Husar: > 16:19:20,809 INFO [org.jboss.modcluster] (management-handler-thread - 3) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/clusterbench in 10 seconds. > 16:19:30,814 WARN [org.jboss.modcluster] (management-handler-thread - 3) MODCLUSTER000025: Failed to drain 1 remaining active sessions from default-host:/clusterbench within 10.0 seconds -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3031) Upgrade WildFly Elytron Web to 1.0.0.CR1

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3031?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-3031: ------------------------------------- Fix Version/s: 3.0.0.Beta28 > Upgrade WildFly Elytron Web to 1.0.0.CR1 > ---------------------------------------- > > Key: WFCORE-3031 > URL: https://issues.jboss.org/browse/WFCORE-3031 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Beta28 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 June 2017