January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-929) CLI is terminated unexpectedly after type "u" on HPUX

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-929?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-929: --------------------------------------- Assignee: Ståle Pedersen (was: Alexey Loubyansky) Resolution: Done > CLI is terminated unexpectedly after type "u" on HPUX > ----------------------------------------------------- > > Key: WFCORE-929 > URL: https://issues.jboss.org/browse/WFCORE-929 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Beta4 > Reporter: Marek Kopecký > Assignee: Ståle Pedersen > Priority: Blocker > Fix For: 2.0.8.Final > > > *Description of problem:* > CLI is terminated unexpectedly after type "qui" on HPUX > *How reproducible:* > Always on HPUX > *Steps to Reproduce:* > # ./standalone.sh > # ./jboss-cli.sh -c > # qui > #* type "qui" in console to CLI, do not press "enter" > *Actual results:* > CLI is terminated > *Expected results:* > CLI is not terminated -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6053) Suggested defaults for Metasize and Java 8

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6053?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-6053: ----------------------------------- Component/s: Domain Management > Suggested defaults for Metasize and Java 8 > ------------------------------------------ > > Key: WFLY-6053 > URL: https://issues.jboss.org/browse/WFLY-6053 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 10.0.0.Final > > > This is the ticket to perform the analogous changes made to core in WFCORE-1319 regarding default MetasizeSpace/ > Since PermGen is no longer used, and has been replaced by Metasize, we probably need to alter the initial startup values. Current WF is using: > -XX:MaxMetaspaceSize=256m > After some testing with garbage collection logging on (\-verbose:gc \-Xloggc:hcgc.log \-XX:+PrintGCDateStamps \-XX:MetaspaceSize=XX), the GC logs were monitored for at least one occurrence of a full GC due to Metadata threshold (example [Full GC (Metadata GC Threshold) 39592K->20187K). Using this information, minimum levels of Metasize for various configurations were determined. > The numbers below are the values used for \-XX:MetaspaceSize=XXM followed by the number of full GCs triggered at that amount measured during boot of WF10-full: > Standalone: > {quote} > standalone.xml 52MB(1), 53MB(0) > standalone-full.xml 64MB(1), 65MB(0) > standalone-ha.xml 52MB(1), 54MB(0) > standalone-full-ha.xml 79MB(1), 80MB(0) > {quote} > For domain mode, the corresponding values were determined to be: > {quote} > Process Controller: 12MB(1), 13MB(0) > Host Controller: 39MB(1), 40MB(0) > {quote} > In domain mode, a very slight, non-scientifically measured boot time difference was observed (1769ms default Metasize vs 1694ms with 40m MetaSize set for host controller). > The approximate cost of increasing MetaSize over the default is summerized below (using top to collect RSS after server boot): > JBoss AS 7.1.1: (default permgen (-XX:PermSize=256m -XX:MaxPermSize=256m), JDK 7) > ||Configuration||RSS(KB)|| > |standalone.xml| 182,652 | > |standalone-ha.xml | 211,672 | > |standalone-full.xml | 217,636 | > |standalone-full-ha.xml | 289,524 | > |domain:|| > | Server-one: | 227,220 | > | Server-two: | 234,944 | > | PC: | 37,584 | > | HC: | 138,428 | > Wildfly 10: (default Metasize == 21M) > ||Configuration||RSS(KB)|| > |standalone.xml | 293,576 | > |standalone-ha.xml | 303,344 | > |standalone-full.xml | 388,660 | > |standalone-full-ha.xml | 478,576 | > |domain: || > | Server-one: | 379,076 | > | Server-two: | 377,516 | > | PC: | 55,000 | > | HC: | 272,120 | > Wildfly 10: (Metasize == 64M) > |standalone.xml | 290,236 | > |standalone-ha.xml | 306,032 | > |standalone-full.xml | 396,596 | > |standalone-full-ha.xml | 501,576 | > |domain:| > | Server-one: | > | Server-two: | > | PC: | > | HC: | > Wildfly 10: (Metasize == 96M) > ||Configuration||RSS(KB)|| > |standalone.xml |317,996 | > |standalone-ha.xml | 306,516 | > |standalone-full.xml |416,008 | > |standalone-full-ha.xml |460,952 | > |domain: | > | Server-one: | 380,816 | > | Server-two: | 374,300 | > | PC: | 55,308 | > | HC: | 273,220 | > Additional measurements. Using just Wildfly-core, the following RSS sizes are measured for the indicated Metasize: > Wildfly-10 Core master > ||Metasize || RSS(KB) || > |21m | 117,760| > |64m | 120,772| > |96m | 131,104| > There is little boot time impact on the change: > Wildfly-10 Core master > ||Metasize || Boot time (MS) || > |21m | 2127 | > |64m | 2066 | > |96m | 2099 | > Based on the memory impact of defaulting to 96M (approx 30mb initially over the default value of 21mb), it would seem to make sense to use this as a default value, which allows maintaining boot times without incurring a full GC due to Metasize and provides enough initial Metasize to both start the application server and perhaps deploy an application without incurring any performance penalty. > An additional note: host*.xml has JVM params set to MetaspaceSize=256m, which is probably too large an initial value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-929) CLI is terminated unexpectedly after type "u" on HPUX

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-929?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-929: ------------------------------------ Fix Version/s: 2.0.8.Final > CLI is terminated unexpectedly after type "u" on HPUX > ----------------------------------------------------- > > Key: WFCORE-929 > URL: https://issues.jboss.org/browse/WFCORE-929 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Beta4 > Reporter: Marek Kopecký > Assignee: Alexey Loubyansky > Fix For: 2.0.8.Final > > > *Description of problem:* > CLI is terminated unexpectedly after type "qui" on HPUX > *How reproducible:* > Always on HPUX > *Steps to Reproduce:* > # ./standalone.sh > # ./jboss-cli.sh -c > # qui > #* type "qui" in console to CLI, do not press "enter" > *Actual results:* > CLI is terminated > *Expected results:* > CLI is not terminated -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-929) CLI is terminated unexpectedly after type "u" on HPUX

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-929?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-929: ------------------------------------ Priority: Blocker (was: Major) > CLI is terminated unexpectedly after type "u" on HPUX > ----------------------------------------------------- > > Key: WFCORE-929 > URL: https://issues.jboss.org/browse/WFCORE-929 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Beta4 > Reporter: Marek Kopecký > Assignee: Alexey Loubyansky > Priority: Blocker > Fix For: 2.0.8.Final > > > *Description of problem:* > CLI is terminated unexpectedly after type "qui" on HPUX > *How reproducible:* > Always on HPUX > *Steps to Reproduce:* > # ./standalone.sh > # ./jboss-cli.sh -c > # qui > #* type "qui" in console to CLI, do not press "enter" > *Actual results:* > CLI is terminated > *Expected results:* > CLI is not terminated -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1202) LDAP authentication/authorization fails due to making unneeded role lookup requests

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1202?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1202: ------------------------------------------------- Brad Maxwell <bmaxwell(a)redhat.com> changed the Status of [bug 1196343|https://bugzilla.redhat.com/show_bug.cgi?id=1196343] from ASSIGNED to ON_QA > LDAP authentication/authorization fails due to making unneeded role lookup requests > ----------------------------------------------------------------------------------- > > Key: WFCORE-1202 > URL: https://issues.jboss.org/browse/WFCORE-1202 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Brad Maxwell > Assignee: Derek Horton > Fix For: 2.0.5.CR1 > > > LDAP authentication/authorization fails due to making unneeded role lookup requests -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6064) Distributed SFSB cache entries may rehash to different nodes following topology change

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-6064: ---------------------------------- Summary: Distributed SFSB cache entries may rehash to different nodes following topology change Key: WFLY-6064 URL: https://issues.jboss.org/browse/WFLY-6064 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.CR5 Reporter: Paul Ferraro Assignee: Paul Ferraro A distributed SFSB is stored in 2 cache entries, one mapping the bean ID to a serialization group ID, and another mapping the group ID to a map of bean instances. We ensure that both cache entries will hash to the local node, but following a topology change, these entries could get re-mapped to different nodes. If we made the group ID = the bean Id of the first bean in the group, this solves the problem for 90% of use cases. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4786) Clustering integration tests fails once -Dnode0 and -Dnode1 are used

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4786?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-4786: --------------------------------- Steps to Reproduce: ./integration-tests.sh clean install -Dmaven.repo.local=$MAVEN_REPO_LOCAL -Dmcast=$MCAST_ADDR -Dts.noSmoke -Dts.clustering -Dtest=org.jboss.as.test.clustering.cluster.\*.\* -Djboss.dist=$JBOSS_DIST -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 (was: ./integration-tests.sh -Dmaven.repo.local=$MAVEN_REPO_LOCAL -Dmcast=$MCAST_ADDR -Dts.noSmoke -Dts.clustering -Dtest=org.jboss.as.test.clustering.cluster.\*.\* -Djboss.dist=$JBOSS_DIST -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2) > Clustering integration tests fails once -Dnode0 and -Dnode1 are used > -------------------------------------------------------------------- > > Key: WFLY-4786 > URL: https://issues.jboss.org/browse/WFLY-4786 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 10.0.0.Alpha3 > Reporter: Petr Kremensky > Assignee: Radoslav Husar > Fix For: 10.0.0.Beta2 > > Attachments: maven.logs, results.zip, testsuite.clustering.logs.zip > > > Tests from wildfly-ts-integ-clustering module fails once we change default binding interfaces by -Dnode0 and -Dnode1 properties. > See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-as-testsuite-... > * build 5 binds to localhost (no -Dnode*) > * build 6 uses -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 > Similar failures were addressed for EAP 6 by https://bugzilla.redhat.com/show_bug.cgi?id=1076015 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3984) Multicast-based clustering testsuite does not work on JDK 8

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3984?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed WFLY-3984. -------------------------------- > Multicast-based clustering testsuite does not work on JDK 8 > ----------------------------------------------------------- > > Key: WFLY-3984 > URL: https://issues.jboss.org/browse/WFLY-3984 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 8.0.0.Final, 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.Beta1 > > > See https://bugzilla.redhat.com/show_bug.cgi?id=1076015 (https://issues.jboss.org/browse/JGRP-1878?focusedCommentId=12999162&page=...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6063) Testsuite: with introduction of "private" default interface there is no need for "multicast" interface in the testsuite

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-6063: ------------------------------------ Summary: Testsuite: with introduction of "private" default interface there is no need for "multicast" interface in the testsuite Key: WFLY-6063 URL: https://issues.jboss.org/browse/WFLY-6063 Project: WildFly Issue Type: Task Components: Clustering, Test Suite Affects Versions: 10.0.0.CR5 Reporter: Radoslav Husar Assignee: Radoslav Husar Which means we can get rid of testsuite/integration/src/test/xslt/changeJGroupsMulticastInterface.xsl and the uses of it. As part of this, we can make this configurable from the testsuite parameters (would that be useful?). Logic was introduced for WFLY-3984. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6063) Testsuite: with introduction of "private" default interface there is no need for "multicast" interface in the testsuite

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6063?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6063: --------------------------------- Priority: Minor (was: Major) > Testsuite: with introduction of "private" default interface there is no need for "multicast" interface in the testsuite > ----------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-6063 > URL: https://issues.jboss.org/browse/WFLY-6063 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 10.0.0.CR5 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > Which means we can get rid of testsuite/integration/src/test/xslt/changeJGroupsMulticastInterface.xsl and the uses of it. > As part of this, we can make this configurable from the testsuite parameters (would that be useful?). > Logic was introduced for WFLY-3984. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 January 2016