June 2016 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-513) Discovery in cloud environments

by Radoslav Husar (JIRA)

Radoslav Husar created MODCLUSTER-513: ----------------------------------------- Summary: Discovery in cloud environments Key: MODCLUSTER-513 URL: https://issues.jboss.org/browse/MODCLUSTER-513 Project: mod_cluster Issue Type: Bug Components: Core & Container Integration (Java), Native (httpd modules) Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 2.0.0.Alpha1 Currently we only support multicast-based discovery and static configuration none of which is suitable for the clouds. Ideally we should generalize discovery and support pluggable implementations (could wildfly-discovery be a starting point?). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-503) Write balancer's address to Azure Blob Storage via its REST api, libcurl

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-503?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-503: ------------------------------------------------ half of the problem is to get httpd (the proxy) to write/publish his address and port so the nodes can read it. > Write balancer's address to Azure Blob Storage via its REST api, libcurl > ------------------------------------------------------------------------ > > Key: MODCLUSTER-503 > URL: https://issues.jboss.org/browse/MODCLUSTER-503 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Environment: Azure > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > > * the Azure Storage C++ lib depends on Casablanca, it's bloatware, too heavy > * we can do with simple libcurl + openssl for generating proper REST requests > * could be done in C without much overhead -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-511) run-demo.sh script fails in most cases

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-511?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-511: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 2.0.0.Alpha1 Resolution: Done > run-demo.sh script fails in most cases > -------------------------------------- > > Key: MODCLUSTER-511 > URL: https://issues.jboss.org/browse/MODCLUSTER-511 > Project: mod_cluster > Issue Type: Bug > Components: Documentation & Demos > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > on a system with smaller ulimit -s > {noformat} > [rhusar@syrah client]$ sh run-demo.sh > run-demo.sh: line 19: 48696 Bus error: 10 java -cp $CP $OPTS org.jboss.modcluster.demo.client.ModClusterDemo > {noformat} > onJDK8: > {noformat} > [rhusar@x220 client]$ sh run-demo.sh > MaxTenuringThreshold of 31 is invalid; must be between 0 and 15 > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-504) Read balancer's address from Azure Blob Storage with Java lib

by Richard Janík (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-504?page=com.atlassian.jira.pl... ] Richard Janík commented on MODCLUSTER-504: ------------------------------------------ As recommended by mbabacek, I'm commenting with "I want this to happen!". I am currently only aware of static discovery option for {{mod_cluster}} in cloud environments, since multicast is usually disabled. This would be a good idea for growing/shrinking clusters in clouds. > Read balancer's address from Azure Blob Storage with Java lib > ------------------------------------------------------------- > > Key: MODCLUSTER-504 > URL: https://issues.jboss.org/browse/MODCLUSTER-504 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Environment: Azure > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > > * take a look at JGroups'-extra Azure ping > * leverage the Azure Java lib so as mod_cluster subsystem in Wildfly and mod_cluster Listener in Tomcat could read balancer's location from the Azure blob storage -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-503) Write balancer's address to Azure Blob Storage via its REST api, libcurl

by Richard Janík (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-503?page=com.atlassian.jira.pl... ] Richard Janík commented on MODCLUSTER-503: ------------------------------------------ As recommended by mbabacek, I'm commenting with "I want this to happen!". I am currently only aware of static discovery option for {{mod_cluster}} in cloud environments, since multicast is usually disabled. This would be a good idea for growing/shrinking clusters in clouds. > Write balancer's address to Azure Blob Storage via its REST api, libcurl > ------------------------------------------------------------------------ > > Key: MODCLUSTER-503 > URL: https://issues.jboss.org/browse/MODCLUSTER-503 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Environment: Azure > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > > * the Azure Storage C++ lib depends on Casablanca, it's bloatware, too heavy > * we can do with simple libcurl + openssl for generating proper REST requests > * could be done in C without much overhead -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-511) run-demo.sh script fails in most cases

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-511?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-511: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/192 > run-demo.sh script fails in most cases > -------------------------------------- > > Key: MODCLUSTER-511 > URL: https://issues.jboss.org/browse/MODCLUSTER-511 > Project: mod_cluster > Issue Type: Bug > Components: Documentation & Demos > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > on a system with smaller ulimit -s > {noformat} > [rhusar@syrah client]$ sh run-demo.sh > run-demo.sh: line 19: 48696 Bus error: 10 java -cp $CP $OPTS org.jboss.modcluster.demo.client.ModClusterDemo > {noformat} > onJDK8: > {noformat} > [rhusar@x220 client]$ sh run-demo.sh > MaxTenuringThreshold of 31 is invalid; must be between 0 and 15 > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-511) run-demo.sh script fails in most cases

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-511?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-511: ------------------------------------------- Actually the first part was already reported: MODCLUSTER-169 > run-demo.sh script fails in most cases > -------------------------------------- > > Key: MODCLUSTER-511 > URL: https://issues.jboss.org/browse/MODCLUSTER-511 > Project: mod_cluster > Issue Type: Bug > Components: Documentation & Demos > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > on a system with smaller ulimit -s > {noformat} > [rhusar@syrah client]$ sh run-demo.sh > run-demo.sh: line 19: 48696 Bus error: 10 java -cp $CP $OPTS org.jboss.modcluster.demo.client.ModClusterDemo > {noformat} > onJDK8: > {noformat} > [rhusar@x220 client]$ sh run-demo.sh > MaxTenuringThreshold of 31 is invalid; must be between 0 and 15 > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-512) Load demo does not work with Undertow: ServletException: Failed to locate jvm route!

by Radoslav Husar (JIRA)

Radoslav Husar created MODCLUSTER-512: ----------------------------------------- Summary: Load demo does not work with Undertow: ServletException: Failed to locate jvm route! Key: MODCLUSTER-512 URL: https://issues.jboss.org/browse/MODCLUSTER-512 Project: mod_cluster Issue Type: Bug Components: Documentation & Demos Affects Versions: 1.3.2.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 2.0.0.Alpha1 {noformat}23:25:27,338 ERROR [io.undertow.request] (default task-36) UT005023: Exception handling request to /mod_cluster-demo-server-2.0.0.Alpha1-SNAPSHOT/record: javax.servlet.ServletException: Failed to locate jvm route! at org.jboss.modcluster.demo.servlet.LoadServlet.init(LoadServlet.java:71) at javax.servlet.GenericServlet.init(GenericServlet.java:244) at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:117) at org.wildfly.extension.undertow.security.RunAsLifecycleInterceptor.init(RunAsLifecycleInterceptor.java:78) at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:103) at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:239) at io.undertow.servlet.core.ManagedServlet.getServlet(ManagedServlet.java:171) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:84) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:285) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:264) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:175) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:792) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-511) run-demo.sh script fails in most cases

by Radoslav Husar (JIRA)

Radoslav Husar created MODCLUSTER-511: ----------------------------------------- Summary: run-demo.sh script fails in most cases Key: MODCLUSTER-511 URL: https://issues.jboss.org/browse/MODCLUSTER-511 Project: mod_cluster Issue Type: Bug Components: Documentation & Demos Reporter: Radoslav Husar Assignee: Radoslav Husar on a system with smaller ulimit -s {noformat} [rhusar@syrah client]$ sh run-demo.sh run-demo.sh: line 19: 48696 Bus error: 10 java -cp $CP $OPTS org.jboss.modcluster.demo.client.ModClusterDemo {noformat} onJDK8: {noformat} [rhusar@x220 client]$ sh run-demo.sh MaxTenuringThreshold of 31 is invalid; must be between 0 and 15 Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-346) :read-proxies-configuration and :read-proxies-info fail when there is no httpd

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-346?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-346: -------------------------------------- Comment: was deleted (was: Aaron Ogburn <aogburn(a)redhat.com> changed the Status of [bug 1343633|https://bugzilla.redhat.com/show_bug.cgi?id=1343633] from NEW to ASSIGNED) > :read-proxies-configuration and :read-proxies-info fail when there is no httpd > ------------------------------------------------------------------------------ > > Key: MODCLUSTER-346 > URL: https://issues.jboss.org/browse/MODCLUSTER-346 > Project: mod_cluster > Issue Type: Bug > Environment: RHEL 6, EAP 6.1.0, mod_cluster-1.2.4-1.Final_redhat_1.ep6.el6.noarch, > Reporter: Kristina Clair > Assignee: Jean-Frederic Clere > > 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)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues June 2016