October 2018 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-664) Upgrade org.apache.httpcomponents:httpclient to 4.3.6

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-664?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-664: -------------------------------------- Summary: Upgrade org.apache.httpcomponents:httpclient to 4.3.6 (was: Upgrade org.apache.httpcomponents:httpclient to >= 4.3.6) > Upgrade org.apache.httpcomponents:httpclient to 4.3.6 > ----------------------------------------------------- > > Key: MODCLUSTER-664 > URL: https://issues.jboss.org/browse/MODCLUSTER-664 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.4.0.Final, 1.3.10.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > https://nvd.nist.gov/vuln/detail/CVE-2015-5262 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-664) Upgrade org.apache.httpcomponents:httpclient to >= 4.3.6

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-664?page=com.atlassian.jira.pl... ] Radoslav Husar reassigned MODCLUSTER-664: ----------------------------------------- Assignee: Radoslav Husar (was: Jean-Frederic Clere) > Upgrade org.apache.httpcomponents:httpclient to >= 4.3.6 > -------------------------------------------------------- > > Key: MODCLUSTER-664 > URL: https://issues.jboss.org/browse/MODCLUSTER-664 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.4.0.Final, 1.3.10.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > https://nvd.nist.gov/vuln/detail/CVE-2015-5262 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-664) Upgrade org.apache.httpcomponents:httpclient to >= 4.3.6

by Radoslav Husar (Jira)

Radoslav Husar created MODCLUSTER-664: ----------------------------------------- Summary: Upgrade org.apache.httpcomponents:httpclient to >= 4.3.6 Key: MODCLUSTER-664 URL: https://issues.jboss.org/browse/MODCLUSTER-664 Project: mod_cluster Issue Type: Bug Components: Core & Container Integration (Java) Affects Versions: 1.3.10.Final, 1.4.0.Final Reporter: Radoslav Husar Assignee: Jean-Frederic Clere https://nvd.nist.gov/vuln/detail/CVE-2015-5262 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-664) Upgrade org.apache.httpcomponents:httpclient to >= 4.3.6

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-664?page=com.atlassian.jira.pl... ] Work on MODCLUSTER-664 started by Radoslav Husar. ------------------------------------------------- > Upgrade org.apache.httpcomponents:httpclient to >= 4.3.6 > -------------------------------------------------------- > > Key: MODCLUSTER-664 > URL: https://issues.jboss.org/browse/MODCLUSTER-664 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.4.0.Final, 1.3.10.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > https://nvd.nist.gov/vuln/detail/CVE-2015-5262 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-663) mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-663?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-663: -------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Merged. > mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely > ------------------------------------------------------------------------------------------------------------------ > > Key: MODCLUSTER-663 > URL: https://issues.jboss.org/browse/MODCLUSTER-663 > Project: mod_cluster > Issue Type: Enhancement > Components: Core & Container Integration (Java) > Affects Versions: 1.4.0.Final, 1.3.10.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > Fix For: 2.0.0.Alpha1, 1.4.1.Final > > > When {{stop}} operation with {{waittime=0}} is called on a mod_cluster node, it wait indefinitely until all sessions time out. However, following line appears in log: > {code} > INFO [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/karel in 0 seconds. > {code} > This could confuse someone looking into the log -- they would then think,that this operation killed sessions even when it didn't. > Suggestion: Replace this message with more accurate one. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-663) mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-663?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-663: -------------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/348, https://github.com/modcluster/mod_cluster/pull/347 (was: https://github.com/modcluster/mod_cluster/pull/347) > mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely > ------------------------------------------------------------------------------------------------------------------ > > Key: MODCLUSTER-663 > URL: https://issues.jboss.org/browse/MODCLUSTER-663 > Project: mod_cluster > Issue Type: Enhancement > Components: Core & Container Integration (Java) > Affects Versions: 1.4.0.Final, 1.3.10.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > Fix For: 2.0.0.Alpha1, 1.4.1.Final > > > When {{stop}} operation with {{waittime=0}} is called on a mod_cluster node, it wait indefinitely until all sessions time out. However, following line appears in log: > {code} > INFO [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/karel in 0 seconds. > {code} > This could confuse someone looking into the log -- they would then think,that this operation killed sessions even when it didn't. > Suggestion: Replace this message with more accurate one. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-663) mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-663?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-663: -------------------------------------- Fix Version/s: 2.0.0.Alpha1 1.4.1.Final > mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely > ------------------------------------------------------------------------------------------------------------------ > > Key: MODCLUSTER-663 > URL: https://issues.jboss.org/browse/MODCLUSTER-663 > Project: mod_cluster > Issue Type: Enhancement > Components: Core & Container Integration (Java) > Affects Versions: 1.4.0.Final, 1.3.10.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > Fix For: 2.0.0.Alpha1, 1.4.1.Final > > > When {{stop}} operation with {{waittime=0}} is called on a mod_cluster node, it wait indefinitely until all sessions time out. However, following line appears in log: > {code} > INFO [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/karel in 0 seconds. > {code} > This could confuse someone looking into the log -- they would then think,that this operation killed sessions even when it didn't. > Suggestion: Replace this message with more accurate one. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-663) mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-663?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-663: -------------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/347 > mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely > ------------------------------------------------------------------------------------------------------------------ > > Key: MODCLUSTER-663 > URL: https://issues.jboss.org/browse/MODCLUSTER-663 > Project: mod_cluster > Issue Type: Enhancement > Components: Core & Container Integration (Java) > Affects Versions: 1.4.0.Final, 1.3.10.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > > When {{stop}} operation with {{waittime=0}} is called on a mod_cluster node, it wait indefinitely until all sessions time out. However, following line appears in log: > {code} > INFO [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/karel in 0 seconds. > {code} > This could confuse someone looking into the log -- they would then think,that this operation killed sessions even when it didn't. > Suggestion: Replace this message with more accurate one. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-663) mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-663?page=com.atlassian.jira.pl... ] Work on MODCLUSTER-663 started by Radoslav Husar. ------------------------------------------------- > mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely > ------------------------------------------------------------------------------------------------------------------ > > Key: MODCLUSTER-663 > URL: https://issues.jboss.org/browse/MODCLUSTER-663 > Project: mod_cluster > Issue Type: Enhancement > Components: Core & Container Integration (Java) > Affects Versions: 1.4.0.Final, 1.3.10.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > > When {{stop}} operation with {{waittime=0}} is called on a mod_cluster node, it wait indefinitely until all sessions time out. However, following line appears in log: > {code} > INFO [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/karel in 0 seconds. > {code} > This could confuse someone looking into the log -- they would then think,that this operation killed sessions even when it didn't. > Suggestion: Replace this message with more accurate one. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-663) mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-663?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-663: -------------------------------------- Issue Type: Enhancement (was: Bug) > mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely > ------------------------------------------------------------------------------------------------------------------ > > Key: MODCLUSTER-663 > URL: https://issues.jboss.org/browse/MODCLUSTER-663 > Project: mod_cluster > Issue Type: Enhancement > Components: Core & Container Integration (Java) > Affects Versions: 1.4.0.Final, 1.3.10.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > > When {{stop}} operation with {{waittime=0}} is called on a mod_cluster node, it wait indefinitely until all sessions time out. However, following line appears in log: > {code} > INFO [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/karel in 0 seconds. > {code} > This could confuse someone looking into the log -- they would then think,that this operation killed sessions even when it didn't. > Suggestion: Replace this message with more accurate one. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues October 2018