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 kfir avraham (JIRA)

[ https://issues.jboss.org/browse/JGRP-2237?page=com.atlassian.jira.plugin.... ] kfir avraham updated JGRP-2237: ------------------------------- Attachment: conf.txt > 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: Server_A.txt, Server_B.txt, conf.txt, 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

1
0
0 / 0

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

by kfir avraham (JIRA)

[ https://issues.jboss.org/browse/JGRP-2237?page=com.atlassian.jira.plugin.... ] kfir avraham commented on JGRP-2237: ------------------------------------ i attached logs from server_A, server_B, and conf file. in this case (after upgrade to version 4.0.8) it is look better but from some reason after a few restarts, server_A doesn't sent a join message to the other machine, and create new view with 'is_coord-true'. any idea what could be the reason for that? BTW, we must to use in ' port_range="0" ', because we want to use only in this port, and it worked perfect in 3.6.11 version (we upgraded the version because security issue). when i set ' port_range="5" ', they not discovered each other from the beginning. > 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: Server_A.txt, Server_B.txt, 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

1
0
0 / 0

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

by kfir avraham (JIRA)

[ https://issues.jboss.org/browse/JGRP-2237?page=com.atlassian.jira.plugin.... ] kfir avraham updated JGRP-2237: ------------------------------- Attachment: Server_A.txt Server_B.txt > 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: Server_A.txt, Server_B.txt, 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

1
0
0 / 0

[JBoss JIRA] (WFLY-9582) server not starting from windows service

by Roshan Royal (JIRA)

[ https://issues.jboss.org/browse/WFLY-9582?page=com.atlassian.jira.plugin.... ] Roshan Royal updated WFLY-9582: ------------------------------- Summary: server not starting from windows service (was: Service is not starting) > server not starting from windows service > ---------------------------------------- > > Key: WFLY-9582 > URL: https://issues.jboss.org/browse/WFLY-9582 > Project: WildFly > Issue Type: Bug > Components: Batch, Server > Affects Versions: 9.0.2.Final > Environment: Window 7 64-bit system > Reporter: Roshan Royal > Assignee: Cheng Fang > Priority: Blocker > > Getting below error while trying to start server through windows service. > [2017-11-29 14:24:47] [info] [14908] Commons Daemon procrun (1.0.15.0 64-bit) started > [2017-11-29 14:24:47] [info] [14908] Starting service 'Wildfly' ... > [2017-11-29 14:24:47] [info] [ 3760] Commons Daemon procrun (1.0.15.0 64-bit) started > [2017-11-29 14:24:47] [info] [ 3760] Running 'Wildfly' Service... > [2017-11-29 14:24:47] [info] [15500] Starting service... > [2017-11-29 14:24:47] [info] [15500] Service started in 3 ms. > [2017-11-29 14:24:47] [info] [ 3760] Run service finished. > [2017-11-29 14:24:47] [info] [ 3760] Commons Daemon procrun finished > [2017-11-29 14:24:48] [error] [14908] Failed to start 'Wildfly' service > [2017-11-29 14:24:48] [error] [14908] The data area passed to a system call is too small. > [2017-11-29 14:24:48] [info] [14908] Start service finished. > [2017-11-29 14:24:48] [error] [14908] Commons Daemon procrun failed with exit value: 5 (Failed to start service) > [2017-11-29 14:24:48] [error] [14908] The data area passed to a system call is too small. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9582) Service is not starting

by Roshan Royal (JIRA)

[ https://issues.jboss.org/browse/WFLY-9582?page=com.atlassian.jira.plugin.... ] Roshan Royal updated WFLY-9582: ------------------------------- Issue Type: Bug (was: Feature Request) > Service is not starting > ----------------------- > > Key: WFLY-9582 > URL: https://issues.jboss.org/browse/WFLY-9582 > Project: WildFly > Issue Type: Bug > Components: Batch, Server > Affects Versions: 9.0.2.Final > Environment: Window 7 64-bit system > Reporter: Roshan Royal > Assignee: Cheng Fang > Priority: Blocker > > Getting below error while trying to start server through windows service. > [2017-11-29 14:24:47] [info] [14908] Commons Daemon procrun (1.0.15.0 64-bit) started > [2017-11-29 14:24:47] [info] [14908] Starting service 'Wildfly' ... > [2017-11-29 14:24:47] [info] [ 3760] Commons Daemon procrun (1.0.15.0 64-bit) started > [2017-11-29 14:24:47] [info] [ 3760] Running 'Wildfly' Service... > [2017-11-29 14:24:47] [info] [15500] Starting service... > [2017-11-29 14:24:47] [info] [15500] Service started in 3 ms. > [2017-11-29 14:24:47] [info] [ 3760] Run service finished. > [2017-11-29 14:24:47] [info] [ 3760] Commons Daemon procrun finished > [2017-11-29 14:24:48] [error] [14908] Failed to start 'Wildfly' service > [2017-11-29 14:24:48] [error] [14908] The data area passed to a system call is too small. > [2017-11-29 14:24:48] [info] [14908] Start service finished. > [2017-11-29 14:24:48] [error] [14908] Commons Daemon procrun failed with exit value: 5 (Failed to start service) > [2017-11-29 14:24:48] [error] [14908] The data area passed to a system call is too small. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9582) Service is not starting

by Roshan Royal (JIRA)

Roshan Royal created WFLY-9582: ---------------------------------- Summary: Service is not starting Key: WFLY-9582 URL: https://issues.jboss.org/browse/WFLY-9582 Project: WildFly Issue Type: Feature Request Components: Batch, Server Affects Versions: 9.0.2.Final Environment: Window 7 64-bit system Reporter: Roshan Royal Assignee: Cheng Fang Priority: Blocker Getting below error while trying to start server through windows service. [2017-11-29 14:24:47] [info] [14908] Commons Daemon procrun (1.0.15.0 64-bit) started [2017-11-29 14:24:47] [info] [14908] Starting service 'Wildfly' ... [2017-11-29 14:24:47] [info] [ 3760] Commons Daemon procrun (1.0.15.0 64-bit) started [2017-11-29 14:24:47] [info] [ 3760] Running 'Wildfly' Service... [2017-11-29 14:24:47] [info] [15500] Starting service... [2017-11-29 14:24:47] [info] [15500] Service started in 3 ms. [2017-11-29 14:24:47] [info] [ 3760] Run service finished. [2017-11-29 14:24:47] [info] [ 3760] Commons Daemon procrun finished [2017-11-29 14:24:48] [error] [14908] Failed to start 'Wildfly' service [2017-11-29 14:24:48] [error] [14908] The data area passed to a system call is too small. [2017-11-29 14:24:48] [info] [14908] Start service finished. [2017-11-29 14:24:48] [error] [14908] Commons Daemon procrun failed with exit value: 5 (Failed to start service) [2017-11-29 14:24:48] [error] [14908] The data area passed to a system call is too small. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3437) CLI can't be started on Solaris

by Marek Kopecký (JIRA)

Marek Kopecký created WFCORE-3437: ------------------------------------- Summary: CLI can't be started on Solaris Key: WFCORE-3437 URL: https://issues.jboss.org/browse/WFCORE-3437 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Marek Kopecký Assignee: Jean-Francois Denise Priority: Critical CLI (WildFly master) can't be started on Solaris: {noformat} [hudson@dev34-02 bin]$ ./jboss-cli.sh You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. java.io.IOException: Error executing 'stty size': unknown mode: size : Error executing 'stty size': unknown mode: size [hudson@dev34-02 bin]$ {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8948) SAML2STSLoginModule cannot be configured with module options instead of configFile

by Vladimir Dosoudil (JIRA)

[ https://issues.jboss.org/browse/WFLY-8948?page=com.atlassian.jira.plugin.... ] Vladimir Dosoudil updated WFLY-8948: ------------------------------------ Labels: downstream_dependency (was: ) > SAML2STSLoginModule cannot be configured with module options instead of configFile > ---------------------------------------------------------------------------------- > > Key: WFLY-8948 > URL: https://issues.jboss.org/browse/WFLY-8948 > Project: WildFly > Issue Type: Bug > Components: EJB, Security > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > Labels: downstream_dependency > > It is not possible to configure the SAML2STSLoginModule by using module options instead of configFile: > <security-domain name="sts" cache-type="default"> > <authentication> > <login-module code="org.picketlink.identity.federation.bindings.jboss.auth.SAML2STSLoginModule" flag="required" module="org.picketlink"> > <module-option name="serviceName" value="PicketLinkSTS"/> > <module-option name="portName" value="PicketLinkSTSPort"/> > <module-option name="endpointAddress" value="http://localhost:8080/picketlink-sts/PicketLinkSTS"/> > <module-option name="username" value="admin"/> > <module-option name="password" value="admin"/> > See BZ for more information. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3435?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3435: ---------------------------------------- Assignee: (was: Jason Greene) > Expose capability/requirements to deployments > --------------------------------------------- > > Key: WFCORE-3435 > URL: https://issues.jboss.org/browse/WFCORE-3435 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 3.0.9.Final > Reporter: Bob McWhirter > > 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

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3435?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3435: ------------------------------------- Component/s: Domain Management > Expose capability/requirements to deployments > --------------------------------------------- > > Key: WFCORE-3435 > URL: https://issues.jboss.org/browse/WFCORE-3435 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > 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

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 November 2017