May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9776) Clustering testsuite: remove reuseFork=false workaround

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-9776?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9776: --------------------------------- Description: This should * simplify the test setup (no single test profile, no -ejb profile) * testsuite speedup was: This should * simplify the setup substantially (no single test profile, no -ejb profile) * speedup > Clustering testsuite: remove reuseFork=false workaround > ------------------------------------------------------- > > Key: WFLY-9776 > URL: https://issues.jboss.org/browse/WFLY-9776 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > This should > * simplify the test setup (no single test profile, no -ejb profile) > * testsuite speedup -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9776) Clustering testsuite: remove reuseFork=false workaround

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-9776?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-9776: -------------------------------------- Looks like this should be possible now with changes in the EJB client. > Clustering testsuite: remove reuseFork=false workaround > ------------------------------------------------------- > > Key: WFLY-9776 > URL: https://issues.jboss.org/browse/WFLY-9776 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > This should > * simplify the setup substantially (no single test profile, no -ejb profile) > * speedup -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9776) Clustering testsuite: remove reuseFork=false workaround

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-9776?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9776: --------------------------------- Description: This should * simplify the setup substantially (no single test profile, no -ejb profile) * speedup > Clustering testsuite: remove reuseFork=false workaround > ------------------------------------------------------- > > Key: WFLY-9776 > URL: https://issues.jboss.org/browse/WFLY-9776 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > This should > * simplify the setup substantially (no single test profile, no -ejb profile) > * speedup -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9776) Clustering testsuite: remove reuseFork=false workaround

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-9776?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9776: --------------------------------- Priority: Critical (was: Major) > Clustering testsuite: remove reuseFork=false workaround > ------------------------------------------------------- > > Key: WFLY-9776 > URL: https://issues.jboss.org/browse/WFLY-9776 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12126) A space in $JAVA path causes bad MODULAR_JDK resolution

by George Trudeau (Jira)

George Trudeau created WFLY-12126: ------------------------------------- Summary: A space in $JAVA path causes bad MODULAR_JDK resolution Key: WFLY-12126 URL: https://issues.jboss.org/browse/WFLY-12126 Project: WildFly Issue Type: Bug Components: Scripts Affects Versions: 17.0.0.Alpha1, 16.0.0.Final Environment: Linux, but it should happen in any environment that uses the bash scripts. I believe it affects all versions of wildly that started supporting the modular JDK. Reporter: George Trudeau When a user setup a JDK in a path containing a space, wildfly yields the following output : {code} ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /tmp/space test/wildfly-16.0.0.Final JAVA: /tmp/space test/jdk-11/bin/java JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true ========================================================================= org.jboss.modules.ModuleNotFoundException: java.se at org.jboss.modules.Module.addPaths(Module.java:1266) at org.jboss.modules.Module.link(Module.java:1622) at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) at org.jboss.modules.Main.main(Main.java:437) {code} The problem lies inside {{bin/common.sh}} : {code:sh} setModularJdk() { $JAVA --add-modules=java.se -version > /dev/null 2>&1 && MODULAR_JDK=true || MODULAR_JDK=false } {code} Since the test fails due to the variable being split, the final $JAVA_OPTS misses options such as {{--add-modules=java.se}}. The $JAVA variable can be quoted to fix the problem : {code:sh} setModularJdk() { "$JAVA" --add-modules=java.se -version > /dev/null 2>&1 && MODULAR_JDK=true || MODULAR_JDK=false } {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12111) Upgrade picketlink to 2.5.5.SP13

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFLY-12111?page=com.atlassian.jira.plugin... ] Teresa Miyar Gil updated WFLY-12111: ------------------------------------ Labels: downstream_dependency (was: ) > Upgrade picketlink to 2.5.5.SP13 > -------------------------------- > > Key: WFLY-12111 > URL: https://issues.jboss.org/browse/WFLY-12111 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Teresa Miyar Gil > Assignee: Teresa Miyar Gil > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12125) Integration test for PLINK-793

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFLY-12125?page=com.atlassian.jira.plugin... ] Teresa Miyar Gil updated WFLY-12125: ------------------------------------ Labels: downstream_dependency (was: ) > Integration test for PLINK-793 > ------------------------------ > > Key: WFLY-12125 > URL: https://issues.jboss.org/browse/WFLY-12125 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 17.0.0.Alpha1 > Reporter: Teresa Miyar Gil > Assignee: Teresa Miyar Gil > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12125) Integration test for PLINK-793

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFLY-12125?page=com.atlassian.jira.plugin... ] Teresa Miyar Gil updated WFLY-12125: ------------------------------------ Summary: Integration test for PLINK-793 (was: Test for PLINK-793) > Integration test for PLINK-793 > ------------------------------ > > Key: WFLY-12125 > URL: https://issues.jboss.org/browse/WFLY-12125 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 17.0.0.Alpha1 > Reporter: Teresa Miyar Gil > Assignee: Teresa Miyar Gil > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12125) Test for PLINK-793

by Teresa Miyar Gil (Jira)

Teresa Miyar Gil created WFLY-12125: --------------------------------------- Summary: Test for PLINK-793 Key: WFLY-12125 URL: https://issues.jboss.org/browse/WFLY-12125 Project: WildFly Issue Type: Task Components: Test Suite Affects Versions: 17.0.0.Alpha1 Reporter: Teresa Miyar Gil Assignee: Teresa Miyar Gil -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

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

by Tommasso Borgato (Jira)

[ https://issues.jboss.org/browse/WFLY-6944?page=com.atlassian.jira.plugin.... ] Tommasso Borgato commented on WFLY-6944: ---------------------------------------- [~pferraro],[~rhusar] which header triggers the multiple routes encoding on WildFly? > 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, 2 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 May 2019