October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3311) embedded server --std-out=discard still causes log output to be shown

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3311?page=com.atlassian.jira.plugi... ] Brian Stansberry reopened WFCORE-3311: -------------------------------------- Reopening in case there was more work wanted. > embedded server --std-out=discard still causes log output to be shown > --------------------------------------------------------------------- > > Key: WFCORE-3311 > URL: https://issues.jboss.org/browse/WFCORE-3311 > Project: WildFly Core > Issue Type: Bug > Reporter: Ken Wills > Assignee: James Perkins > Fix For: 4.0.0.Alpha1 > > > [disconnected /] embed-server --std-out=discard > 10:27:43,671 INFO [org.jboss.modules] (CLI command executor) JBoss Modules version 1.6.1.Final > 10:27:43,698 INFO [org.jboss.as] (MSC service thread 2-8) WFLYSRV0049: WildFly Core 4.0.0.Alpha1-SNAPSHOT "Kenny" starting > ... etc -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3311) embedded server --std-out=discard still causes log output to be shown

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3311?page=com.atlassian.jira.plugi... ] Brian Stansberry edited comment on WFCORE-3311 at 10/5/17 11:28 AM: -------------------------------------------------------------------- Reopening in case there was more work planned. was (Author: brian.stansberry): Reopening in case there was more work wanted. > embedded server --std-out=discard still causes log output to be shown > --------------------------------------------------------------------- > > Key: WFCORE-3311 > URL: https://issues.jboss.org/browse/WFCORE-3311 > Project: WildFly Core > Issue Type: Bug > Reporter: Ken Wills > Assignee: James Perkins > Fix For: 4.0.0.Alpha1 > > > [disconnected /] embed-server --std-out=discard > 10:27:43,671 INFO [org.jboss.modules] (CLI command executor) JBoss Modules version 1.6.1.Final > 10:27:43,698 INFO [org.jboss.as] (MSC service thread 2-8) WFLYSRV0049: WildFly Core 4.0.0.Alpha1-SNAPSHOT "Kenny" starting > ... etc -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3311) embedded server --std-out=discard still causes log output to be shown

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3311?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFCORE-3311. -------------------------------------- Fix Version/s: 4.0.0.Alpha1 Resolution: Done [~jamezp] I assumed this could be resolved with the logging upgrade. > embedded server --std-out=discard still causes log output to be shown > --------------------------------------------------------------------- > > Key: WFCORE-3311 > URL: https://issues.jboss.org/browse/WFCORE-3311 > Project: WildFly Core > Issue Type: Bug > Reporter: Ken Wills > Assignee: James Perkins > Fix For: 4.0.0.Alpha1 > > > [disconnected /] embed-server --std-out=discard > 10:27:43,671 INFO [org.jboss.modules] (CLI command executor) JBoss Modules version 1.6.1.Final > 10:27:43,698 INFO [org.jboss.as] (MSC service thread 2-8) WFLYSRV0049: WildFly Core 4.0.0.Alpha1-SNAPSHOT "Kenny" starting > ... etc -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9420) Partitions can take up to 2 minutes to merge

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9420?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9420: --------------------------------- Description: Using the {{MERGE3}} protocol, it can take significantly longer than {{max_interval}} for merge to happen. The info sender interval is up to 45 seconds {code:java} public long nextInterval() { return Math.max(min_interval, Util.random(max_interval) + max_interval/2); } {code} and the view consistency checker interval is 48 seconds {code:java} protected long computeCheckInterval() { return (long)(max_interval * 1.6); } {code} which depending on the timing can take significant amount of time. was: Using the {{MERGE3}} protocol, it can take significantly longer than {{max_interval}} for merge to happen. The info sender interval is up to 45 seconds {code} public long nextInterval() { return Math.max(min_interval, Util.random(max_interval) + max_interval/2); } {code} and the view consistency checker interval is 48 seconds {code} protected long computeCheckInterval() { return (long)(max_interval * 1.6); } {code} which depending on the timing can take significant amount of time. > Partitions can take up to 2 minutes to merge > -------------------------------------------- > > Key: WFLY-9420 > URL: https://issues.jboss.org/browse/WFLY-9420 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.CR1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: partition_handling > > Using the {{MERGE3}} protocol, it can take significantly longer than {{max_interval}} for merge to happen. > The info sender interval is up to 45 seconds > {code:java} > public long nextInterval() { > return Math.max(min_interval, Util.random(max_interval) + max_interval/2); > } > {code} > and the view consistency checker interval is 48 seconds > {code:java} > protected long computeCheckInterval() { > return (long)(max_interval * 1.6); > } > {code} > which depending on the timing can take significant amount of time. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9420) Cluster partitions can take up to 2 minutes to merge

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9420?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9420: --------------------------------- Summary: Cluster partitions can take up to 2 minutes to merge (was: Partitions can take up to 2 minutes to merge) > Cluster partitions can take up to 2 minutes to merge > ---------------------------------------------------- > > Key: WFLY-9420 > URL: https://issues.jboss.org/browse/WFLY-9420 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.CR1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: partition_handling > > Using the {{MERGE3}} protocol, it can take significantly longer than {{max_interval}} for merge to happen. > The info sender interval is up to 45 seconds > {code:java} > public long nextInterval() { > return Math.max(min_interval, Util.random(max_interval) + max_interval/2); > } > {code} > and the view consistency checker interval is 48 seconds > {code:java} > protected long computeCheckInterval() { > return (long)(max_interval * 1.6); > } > {code} > which depending on the timing can take significant amount of time. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9420) Cluster partitions can take up to 2 minutes to merge

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9420?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9420: --------------------------------- Labels: partition_handling (was: ) > Cluster partitions can take up to 2 minutes to merge > ---------------------------------------------------- > > Key: WFLY-9420 > URL: https://issues.jboss.org/browse/WFLY-9420 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.CR1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: partition_handling > > Using the {{MERGE3}} protocol, it can take significantly longer than {{max_interval}} for merge to happen. > The info sender interval is up to 45 seconds > {code:java} > public long nextInterval() { > return Math.max(min_interval, Util.random(max_interval) + max_interval/2); > } > {code} > and the view consistency checker interval is 48 seconds > {code:java} > protected long computeCheckInterval() { > return (long)(max_interval * 1.6); > } > {code} > which depending on the timing can take significant amount of time. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9420) Partitions can take up to 2 minutes to merge

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9420?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9420: --------------------------------- Description: Using the {{MERGE3}} protocol, it can take significantly longer than {{max_interval}} for merge to happen. The info sender interval is up to 45 seconds {code} public long nextInterval() { return Math.max(min_interval, Util.random(max_interval) + max_interval/2); } {code} and the view consistency checker interval is 48 seconds {code} protected long computeCheckInterval() { return (long)(max_interval * 1.6); } {code} which depending on the timing can take significant amount of time. was: Using the {{MERGE3}} protocol, it can take significantly longer than {{max_interval}} for merge to happen. The info sender interval is up to 45 seconds {noformat} public long nextInterval() { return Math.max(min_interval, Util.random(max_interval) + max_interval/2); } {noformat} and the view consistency checker interval is 48 seconds {noformat} protected long computeCheckInterval() { return (long)(max_interval * 1.6); } {noformat} > Partitions can take up to 2 minutes to merge > -------------------------------------------- > > Key: WFLY-9420 > URL: https://issues.jboss.org/browse/WFLY-9420 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.CR1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Using the {{MERGE3}} protocol, it can take significantly longer than {{max_interval}} for merge to happen. > The info sender interval is up to 45 seconds > {code} > public long nextInterval() { > return Math.max(min_interval, Util.random(max_interval) + max_interval/2); > } > {code} > and the view consistency checker interval is 48 seconds > {code} > protected long computeCheckInterval() { > return (long)(max_interval * 1.6); > } > {code} > which depending on the timing can take significant amount of time. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9420) Partitions can take up to 2 minutes to merge

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-9420: ------------------------------------ Summary: Partitions can take up to 2 minutes to merge Key: WFLY-9420 URL: https://issues.jboss.org/browse/WFLY-9420 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 11.0.0.CR1 Reporter: Radoslav Husar Assignee: Radoslav Husar Using the {{MERGE3}} protocol, it can take significantly longer than {{max_interval}} for merge to happen. The info sender interval is up to 45 seconds {noformat} public long nextInterval() { return Math.max(min_interval, Util.random(max_interval) + max_interval/2); } {noformat} and the view consistency checker interval is 48 seconds {noformat} protected long computeCheckInterval() { return (long)(max_interval * 1.6); } {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBREM-1339) CLI with 2-way SSL often hangs/times out

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/JBREM-1339?page=com.atlassian.jira.plugin... ] Panagiotis Sotiropoulos commented on JBREM-1339: ------------------------------------------------ Adding a PR that reverts https://github.com/jboss-remoting/jboss-remoting/commit/e7a17c3cca653c125... : https://github.com/jboss-remoting/jboss-remoting/pull/147 which seems to be the cause. > CLI with 2-way SSL often hangs/times out > ---------------------------------------- > > Key: JBREM-1339 > URL: https://issues.jboss.org/browse/JBREM-1339 > Project: JBoss Remoting > Issue Type: Bug > Affects Versions: External_issues > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > > Ref : https://bugzilla.redhat.com/show_bug.cgi?id=1491965 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3328) Incorrect licenses in core-feature-pack

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3328?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3328: ------------------------------------- Security: (was: Red Hat Internal) > Incorrect licenses in core-feature-pack > --------------------------------------- > > Key: WFCORE-3328 > URL: https://issues.jboss.org/browse/WFCORE-3328 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 3.0.3.Final, 3.0.4.Final > Reporter: Petr Sakař > Assignee: Petr Sakař > Priority: Critical > Fix For: 4.0.0.Alpha1, 3.0.5.Final > > > {{xerces:xercesImpl:2.11.0.SP5}} contains these licenses in lcore-feature-pack-licenses.xml: > {code} > <license> > <name>Apache License 2.0</name> > <url>http://www.apache.org/licenses/LICENSE-2.0</url> > <distribution>repo</distribution> > </license> > <license> > <name>ICU License - ICU 1.8.1 to ICU 57.1</name> > <url>http://source.icu-project.org/repos/icu/tags/release-57-1/icu4j/main/shar...</url> > <distribution>repo</distribution> > </license> > <license> > <name>Sax Public Domain Notice</name> > <url>http://www.saxproject.org/copying.html</url> > <distribution>repo</distribution> > </license> > <license> > <name>W3C Document License</name> > <url>http://www.w3.org/Consortium/Legal/copyright-documents</url> > <distribution>repo</distribution> > </license> > <license> > <name>W3C Software Notice and Document License (2002-12-31)</name> > <url>https://spdx.org/licenses/W3C.html#licenseText</url> > <distribution>repo</distribution> > </license> > {code} > However, readme and pom only contains ASL. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2017