November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2237) The single node in the cluster not become a coordinator after coordinator leave.

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2237?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2237: -------------------------------- Have you tried this with the config I attached (test.xml)? And please use the latest 4.0.8 to test; this is what I used and I never hit a problem. Your log shows the member waited for 30s which is impossible as {{GMS.timeout}} is 3s in the config you attached! So either you used the wrong config, or attached the wrong config! > The single node in the cluster not become a coordinator after coordinator leave. > -------------------------------------------------------------------------------- > > Key: JGRP-2237 > URL: https://issues.jboss.org/browse/JGRP-2237 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.2, 4.0.8 > Reporter: kfir avraham > Assignee: Bela Ban > Priority: Minor > Attachments: test.xml > > > I got cluster with 2 members, sometimes when the first node (coordinator) leave the cluster the second one is not become a coordinator. > When the first one is rejoin, he could not determine coordinator and select new one from the nodes list. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2238) KUBE_PING should read old env variables and should warn

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2238?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2238: --------------------------- Fix Version/s: 4.0.9 > KUBE_PING should read old env variables and should warn > ------------------------------------------------------- > > Key: JGRP-2238 > URL: https://issues.jboss.org/browse/JGRP-2238 > Project: JGroups > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 4.0.9 > > > While I was upgrading Infinispan cluster on docker, I realised I was using old environment properties. These were neither read nor was any WARN messages being reported. > The code should read the current properties and if not present should try to read the old ones and assign them. Then, we should check if both new and old properties are in use and we should also check if only old ones in use. Both scenarios should warn the user. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9580) Drop ASYNC variant of the clustering testsuite

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9580?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-9580: ------------------------------------ Assignee: Radoslav Husar (was: Jason Greene) > Drop ASYNC variant of the clustering testsuite > ---------------------------------------------- > > Key: WFLY-9580 > URL: https://issues.jboss.org/browse/WFLY-9580 > Project: WildFly > Issue Type: Task > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Cuts the time in half when running {{-DextendedTests}}. This can be dropped since we are moving to Infinispan 9.x,. see http://infinispan.org/docs/9.0.x/upgrading/upgrading.html#removed_async_t... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9580) Drop ASYNC variant of the clustering testsuite

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9580?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9580: --------------------------------- Component/s: Clustering Test Suite > Drop ASYNC variant of the clustering testsuite > ---------------------------------------------- > > Key: WFLY-9580 > URL: https://issues.jboss.org/browse/WFLY-9580 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Cuts the time in half when running {{-DextendedTests}}. This can be dropped since we are moving to Infinispan 9.x,. see http://infinispan.org/docs/9.0.x/upgrading/upgrading.html#removed_async_t... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9580) Drop ASYNC variant of the clustering testsuite

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9580?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9580: --------------------------------- Affects Version/s: 11.0.0.Final > Drop ASYNC variant of the clustering testsuite > ---------------------------------------------- > > Key: WFLY-9580 > URL: https://issues.jboss.org/browse/WFLY-9580 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Cuts the time in half when running {{-DextendedTests}}. This can be dropped since we are moving to Infinispan 9.x,. see http://infinispan.org/docs/9.0.x/upgrading/upgrading.html#removed_async_t... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9580) Drop ASYNC variant of the clustering testsuite

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-9580: ------------------------------------ Summary: Drop ASYNC variant of the clustering testsuite Key: WFLY-9580 URL: https://issues.jboss.org/browse/WFLY-9580 Project: WildFly Issue Type: Task Reporter: Radoslav Husar Assignee: Jason Greene Cuts the time in half when running {{-DextendedTests}}. This can be dropped since we are moving to Infinispan 9.x,. see http://infinispan.org/docs/9.0.x/upgrading/upgrading.html#removed_async_t... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9579) Missing JSF 2.2 taglib files in the implementation JARs

by Evandro Pomatti (JIRA)

[ https://issues.jboss.org/browse/WFLY-9579?page=com.atlassian.jira.plugin.... ] Evandro Pomatti updated WFLY-9579: ---------------------------------- Description: Two recent JSF tablibs are not shipped with the implementation JAR: * Passthrough - "http://xmlns.jcp.org/jsf/passthrough" * Friendly Markup - "http://xmlns.jcp.org/jsf" This doesn't cause any runtime problem, but the IDEs are not able to interpret the XML tags, showing warnings and not giving code suggestions. In-depth details can be found in Stackoverflow: https://stackoverflow.com/q/40865120 was: Two recent JSF tablibs are not shipped with the implementation JAR: * Passthrough - "http://xmlns.jcp.org/jsf/passthrough" * Friendly Markup - "http://xmlns.jcp.org/jsf" This doesn't cause any runtime problem, but the IDEs are not able to interpret the XML tags, showing warnings and not giving code suggestions. In-depth details can be found in Stackoverflow: https://stackoverflow.com/q/40865120/3231778 > Missing JSF 2.2 taglib files in the implementation JARs > ------------------------------------------------------- > > Key: WFLY-9579 > URL: https://issues.jboss.org/browse/WFLY-9579 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 11.0.0.Final > Reporter: Evandro Pomatti > Assignee: Farah Juma > > Two recent JSF tablibs are not shipped with the implementation JAR: > * Passthrough - "http://xmlns.jcp.org/jsf/passthrough" > * Friendly Markup - "http://xmlns.jcp.org/jsf" > This doesn't cause any runtime problem, but the IDEs are not able to interpret the XML tags, showing warnings and not giving code suggestions. > In-depth details can be found in Stackoverflow: https://stackoverflow.com/q/40865120 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9579) Missing JSF 2.2 taglib files in the implementation JARs

by Evandro Pomatti (JIRA)

[ https://issues.jboss.org/browse/WFLY-9579?page=com.atlassian.jira.plugin.... ] Evandro Pomatti updated WFLY-9579: ---------------------------------- Description: Two recent JSF tablibs are not shipped with the implementation JAR: * Passthrough - "http://xmlns.jcp.org/jsf/passthrough" * Friendly Markup - "http://xmlns.jcp.org/jsf" This doesn't cause any runtime problem, but the IDEs are not able to interpret the XML tags, showing warnings and not giving code suggestions. In-depth details can be found in Stackoverflow: https://stackoverflow.com/q/40865120/3231778 was: Two recent JSF tablibs are not shipped with the implementation JAR: * Passthrough - "http://xmlns.jcp.org/jsf/passthrough" * Friendly Markup - "http://xmlns.jcp.org/jsf" This doesn't cause any runtime problem, but the IDEs are not able to interpret the XML tags, showing warnings and not giving code suggestions. In-depth details can be found in Stackoverflow: > Missing JSF 2.2 taglib files in the implementation JARs > ------------------------------------------------------- > > Key: WFLY-9579 > URL: https://issues.jboss.org/browse/WFLY-9579 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 11.0.0.Final > Reporter: Evandro Pomatti > Assignee: Farah Juma > > Two recent JSF tablibs are not shipped with the implementation JAR: > * Passthrough - "http://xmlns.jcp.org/jsf/passthrough" > * Friendly Markup - "http://xmlns.jcp.org/jsf" > This doesn't cause any runtime problem, but the IDEs are not able to interpret the XML tags, showing warnings and not giving code suggestions. > In-depth details can be found in Stackoverflow: https://stackoverflow.com/q/40865120/3231778 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9579) Missing JSF 2.2 taglib files in the implementation JARs

by Evandro Pomatti (JIRA)

Evandro Pomatti created WFLY-9579: ------------------------------------- Summary: Missing JSF 2.2 taglib files in the implementation JARs Key: WFLY-9579 URL: https://issues.jboss.org/browse/WFLY-9579 Project: WildFly Issue Type: Bug Components: JSF Affects Versions: 11.0.0.Final Reporter: Evandro Pomatti Assignee: Farah Juma Two recent JSF tablibs are not shipped with the implementation JAR: * Passthrough - "http://xmlns.jcp.org/jsf/passthrough" * Friendly Markup - "http://xmlns.jcp.org/jsf" This doesn't cause any runtime problem, but the IDEs are not able to interpret the XML tags, showing warnings and not giving code suggestions. In-depth details can be found in Stackoverflow: -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3435) Expose capability/requirements to deployments

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3435?page=com.atlassian.jira.plugi... ] Tomaz Cerar commented on WFCORE-3435: ------------------------------------- We should probably introduce something like CapabilityActivator. Less breaking change would be having ServiceActivatorContext or implement some other interface that would also expose capabilities or have serviceTarget return CapabilityServiceTarget. But both of this options would require that cast is done in ServiceActivator which could case other issues. > Expose capability/requirements to deployments > --------------------------------------------- > > Key: WFCORE-3435 > URL: https://issues.jboss.org/browse/WFCORE-3435 > Project: WildFly Core > Issue Type: Enhancement > Affects Versions: 3.0.9.Final > Reporter: Bob McWhirter > Assignee: Jason Greene > > For WildFly Swarm, we use a fair amount of ServiceActivators in deployments. > Moving to WF11, we have seen some of our dependencies on Service<T>, such as NamingService.SERVICE_NAME result in deprecation warnings suggesting we move to using CAPABILITY_NAME. From within a ServiceActivator, within a deployment, this appears to not be a possibility. > Filed per [~ctomc] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 November 2017