June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6781) Wildfly cluster's failover functionality doesn't work as expected

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-6781: ------------------------------------ You description is still missing some crucial details. Are your nodes running on the same host? If you disable networking on the host, and your nodes are both running on that host, how could failover possibly work? For scenario #2, it is certainly possible that windows does not disconnect the socket used by FD_SOCK (if so, this would be a shortcoming of your VM implementation) - consequently, failures are not detected immediately. However, it should be detected by FD_ALL after it fails to receive a heartbeat response after the given timeout. Third - I have no idea how exactly you've determined that "failover isn't working". Can you be more specific? > Wildfly cluster's failover functionality doesn't work as expected > ----------------------------------------------------------------- > > Key: WFLY-6781 > URL: https://issues.jboss.org/browse/WFLY-6781 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.2.0.Final > Reporter: Preeta Kuruvilla > Assignee: Paul Ferraro > Priority: Blocker > > Following are the testing scenarios we did and the outcome:- > 1. Network disabling on a VM for testing failover – Not working for both Linux and Windows environment. > 2. Power off of a VM using VMware client for testing failover – Is working on Linux environment but not working on windows environment. > 3. Ctrl + C method to stop services on a node for testing failover – works on both linux and windows environment > 4. Stopping server running on Node /VM using Admin Console for testing failover - works on both linux and windows environment. > Jgroups subsystem configuration in domain.xml we have is below:- > <subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="udp"> > <stack name="udp"> > <transport type="UDP" socket-binding="jgroups-udp"/> > <protocol type="PING"/> > <protocol type="MERGE3"/> > <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> > <protocol type="FD_ALL"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="UFC"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > <stack name="tcp"> > <transport type="TCP" socket-binding="jgroups-tcp"/> > <protocol type="MPING" socket-binding="jgroups-mping"/> > <protocol type="MERGE2"/> > <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/> > <protocol type="FD"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > </subsystem> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1625) Operation description is not complete in :read-resource-description

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFCORE-1625: ----------------------------------- Summary: Operation description is not complete in :read-resource-description Key: WFCORE-1625 URL: https://issues.jboss.org/browse/WFCORE-1625 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 3.0.0.Alpha2 Reporter: Jeff Mesnil Assignee: Brian Stansberry The ouput of :read-resource-description is missing some metadata for operations compared to :read-operation-description: {noformat} [domain@localhost:9990 /] /profile=default:read-resource-description(operations=true) { "outcome" => "success", "result" => { "description" => "A named set of subsystem configurations.", ... "operations" => { ... "read-attribute-group-names" => { "operation-name" => "read-attribute-group-names", "description" => "Gets the names of all the attribute groups under the selected resource", "request-properties" => {}, "reply-properties" => { "type" => LIST, "value-type" => STRING } }, ... } [domain@localhost:9990 /] /profile=default:read-operation-description(name=read-attribute-group-names) { "outcome" => "success", "result" => { "operation-name" => "read-attribute-group-names", "description" => "Gets the names of all the attribute groups under the selected resource", "request-properties" => {}, "reply-properties" => { "type" => LIST, "value-type" => STRING }, "read-only" => true, "runtime-only" => true } } {noformat} At least read-only and runtime-only metadata are missing (when they are set on the operation). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6780) could not spécify version 3 for ldap connection

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6780?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-6780: --------------------------------- Assignee: Darran Lofthouse (was: Jason Greene) > could not spécify version 3 for ldap connection > ----------------------------------------------- > > Key: WFLY-6780 > URL: https://issues.jboss.org/browse/WFLY-6780 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: cyril leclerc > Assignee: Darran Lofthouse > > HI, > in case of using LDAPExtLoginModule and ldap realm if in active directory there is more than 1000 groups it returns an error : > Caused by: javax.naming.SizeLimitExceededException: [LDAP: error code 4 - Sizelimit Exceeded]; remaining name 'CN=Users,DC=realad,DC=ad' > i can't change in AD the MAXPAGESIZE parameter and i can't specify the module to use version 3 of ldap how i can do ? > it is a big issue for me -) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6780) could not spécify version 3 for ldap connection

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6780?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-6780: ----------------------------------- What version of WildFly / JDK? > could not spécify version 3 for ldap connection > ----------------------------------------------- > > Key: WFLY-6780 > URL: https://issues.jboss.org/browse/WFLY-6780 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: cyril leclerc > Assignee: Darran Lofthouse > > HI, > in case of using LDAPExtLoginModule and ldap realm if in active directory there is more than 1000 groups it returns an error : > Caused by: javax.naming.SizeLimitExceededException: [LDAP: error code 4 - Sizelimit Exceeded]; remaining name 'CN=Users,DC=realad,DC=ad' > i can't change in AD the MAXPAGESIZE parameter and i can't specify the module to use version 3 of ldap how i can do ? > it is a big issue for me -) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6780) could not spécify version 3 for ldap connection

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6780?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-6780: ------------------------------ Component/s: Security > could not spécify version 3 for ldap connection > ----------------------------------------------- > > Key: WFLY-6780 > URL: https://issues.jboss.org/browse/WFLY-6780 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: cyril leclerc > Assignee: Jason Greene > > HI, > in case of using LDAPExtLoginModule and ldap realm if in active directory there is more than 1000 groups it returns an error : > Caused by: javax.naming.SizeLimitExceededException: [LDAP: error code 4 - Sizelimit Exceeded]; remaining name 'CN=Users,DC=realad,DC=ad' > i can't change in AD the MAXPAGESIZE parameter and i can't specify the module to use version 3 of ldap how i can do ? > it is a big issue for me -) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-580) Add the ability to filter out unavailable mechanisms using the MechanismConfigurationSelector once the host name and protocol name are known

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-580?page=com.atlassian.jira.plugin.sy... ] Farah Juma updated ELY-580: --------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/457, https://github.com/wildfly-security/wildfly-elytron/pull/460 (was: https://github.com/wildfly-security/wildfly-elytron/pull/457) > Add the ability to filter out unavailable mechanisms using the MechanismConfigurationSelector once the host name and protocol name are known > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-580 > URL: https://issues.jboss.org/browse/ELY-580 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Authentication Mechanisms, HTTP > Reporter: Farah Juma > Assignee: Farah Juma > > We could modify the {{HttpServerAuthenticationMechanism}} mechanism supplier to take an {{HttpServerRequest}} parameter in order to filter out unavailable mechanisms. (For HTTP auth, the host name and protocol name are obtained using the {{HttpServerRequest}}). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2645) SFSB containing injected DataSource fails to passivate/serialize

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2645?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2645: ----------------------------------------------- Jiří Bílek <jbilek(a)redhat.com> changed the Status of [bug 901300|https://bugzilla.redhat.com/show_bug.cgi?id=901300] from ON_QA to VERIFIED > SFSB containing injected DataSource fails to passivate/serialize > ---------------------------------------------------------------- > > Key: WFLY-2645 > URL: https://issues.jboss.org/browse/WFLY-2645 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Stefano Maestri > Priority: Critical > > See JBPAPP6-1762 for details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6781) Wildfly cluster's failover functionality doesn't work as expected

by Preeta Kuruvilla (JIRA)

[ https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin.... ] Preeta Kuruvilla commented on WFLY-6781: ---------------------------------------- To answer to your question about our using the old version of wildfly, we have this already in production and at that time we used the version that was available. We are considering to upgrade to new version in near future. > Wildfly cluster's failover functionality doesn't work as expected > ----------------------------------------------------------------- > > Key: WFLY-6781 > URL: https://issues.jboss.org/browse/WFLY-6781 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.2.0.Final > Reporter: Preeta Kuruvilla > Assignee: Paul Ferraro > Priority: Blocker > > Following are the testing scenarios we did and the outcome:- > 1. Network disabling on a VM for testing failover – Not working for both Linux and Windows environment. > 2. Power off of a VM using VMware client for testing failover – Is working on Linux environment but not working on windows environment. > 3. Ctrl + C method to stop services on a node for testing failover – works on both linux and windows environment > 4. Stopping server running on Node /VM using Admin Console for testing failover - works on both linux and windows environment. > Jgroups subsystem configuration in domain.xml we have is below:- > <subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="udp"> > <stack name="udp"> > <transport type="UDP" socket-binding="jgroups-udp"/> > <protocol type="PING"/> > <protocol type="MERGE3"/> > <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> > <protocol type="FD_ALL"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="UFC"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > <stack name="tcp"> > <transport type="TCP" socket-binding="jgroups-tcp"/> > <protocol type="MPING" socket-binding="jgroups-mping"/> > <protocol type="MERGE2"/> > <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/> > <protocol type="FD"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > </subsystem> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6781) Wildfly cluster's failover functionality doesn't work as expected

by Preeta Kuruvilla (JIRA)

[ https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin.... ] Preeta Kuruvilla commented on WFLY-6781: ---------------------------------------- That was a good explanation. Thanks Paul. Never knew about the loopback interface before while I was configuring. We have this configuration in our domain.xml <interfaces> <interface name="management"> <inet-address value="${jboss.bind.address.management:10.76.82.121}"/> </interface> <interface name="public"> <inet-address value="${jboss.bind.address:10.76.82.121}"/> </interface> <interface name="unsecure"> <inet-address value="${jboss.bind.address.unsecure:10.76.82.121}"/> </interface> </interfaces> where the bind-address is the ip-address of the VM. Thanks, Preeta > Wildfly cluster's failover functionality doesn't work as expected > ----------------------------------------------------------------- > > Key: WFLY-6781 > URL: https://issues.jboss.org/browse/WFLY-6781 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.2.0.Final > Reporter: Preeta Kuruvilla > Assignee: Paul Ferraro > Priority: Blocker > > Following are the testing scenarios we did and the outcome:- > 1. Network disabling on a VM for testing failover – Not working for both Linux and Windows environment. > 2. Power off of a VM using VMware client for testing failover – Is working on Linux environment but not working on windows environment. > 3. Ctrl + C method to stop services on a node for testing failover – works on both linux and windows environment > 4. Stopping server running on Node /VM using Admin Console for testing failover - works on both linux and windows environment. > Jgroups subsystem configuration in domain.xml we have is below:- > <subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="udp"> > <stack name="udp"> > <transport type="UDP" socket-binding="jgroups-udp"/> > <protocol type="PING"/> > <protocol type="MERGE3"/> > <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> > <protocol type="FD_ALL"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="UFC"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > <stack name="tcp"> > <transport type="TCP" socket-binding="jgroups-tcp"/> > <protocol type="MPING" socket-binding="jgroups-mping"/> > <protocol type="MERGE2"/> > <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/> > <protocol type="FD"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > </subsystem> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6680) :read-proxies-configuration and :read-proxies-info fail when at least one of the proxies is unreachable

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-6680?page=com.atlassian.jira.plugin.... ] Carlo de Wolf updated WFLY-6680: -------------------------------- Labels: downstream_dependency (was: ) > :read-proxies-configuration and :read-proxies-info fail when at least one of the proxies is unreachable > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-6680 > URL: https://issues.jboss.org/browse/WFLY-6680 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Environment: RHEL 6, EAP 6.1.0, mod_cluster-1.2.4-1.Final_redhat_1.ep6.el6.noarch, > Reporter: Kristina Clair > Assignee: Radoslav Husar > Labels: downstream_dependency > Fix For: 10.1.0.Final > > > When the modcluster subsystem is unable to connect to a proxy, the jboss-cli commands :read-proxies-configuration and :read-proxies-info fail with an unhelpful error. > On both the domain controller and application host, :read-proxies-info and :read-proxies-configuration fail with the same error. This is the output from the application host: > {noformat} > [domain@localhost:9999 subsystem=modcluster] pwd > /host=localhost/server=cluster2/subsystem=modcluster > [domain@localhost:9999 subsystem=modcluster] :list-proxies > { > "outcome" => "success", > "result" => [ > "web02:8009", > "web01:8009" > ] > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-configuration > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-info > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > {noformat} > In the above example, modcluster was not able to connect to the proxies due to an ssl misconfiguration in the modcluster subsystem in domain.xml. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016