I'm using a rabbitmq ha cluster with the ha-proxy load balancer. Now I'm trying to connect to my load balancer from rebus but I don't know how to setup the connectionstring for rebus. When I connect to the nodes individually by their connection string it works well (eg:amqp://test:test#10.182.40.68:5672 ). Only when I modify the connectionstring to use the load balancer it does not work. My load balancer connectionstring is amqp://rabbit.chathuri.local:5670 (but I tried amqp://test:test#rabbit.chathuri.local:5670 and amqp://test:test#rabbit.chathuri.local connection strings as well, they also didnt work. But My load balancer is working as I can ping rabbit.chathuri.local). Can you please tell me what I'm doing wrong?
Related
Following along from the Use a static IP address with the Azure Container Service (AKS) load balancer documentation I have created a static IP and assigned it to the load balancer. This worked fine on the initial run, but now I am getting the following error and the external ip for my load balancer is stuck <pending> (personal info omitted):
Failed to ensure load balancer for service default/[...]: network.LoadBalancersClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="PublicIPReferencedByMultipleIPConfigs" Message="Public ip address /subscriptions/[...]/providers/Microsoft.Network/publicIPAddresses/[PublicIPName] is referenced by multiple ipconfigs in resource
As far as I can tell, this isn't referenced by multiple configs - just the load balancer service that I'm trying to run. Removing the loadBalancerIP option from my yaml file allows this to work but then I don't think the server address is static - which is not ideal for the applications trying to communicate with this container
Is this supposed to be happening? Is there a way to configure this so that the same IP can be reused after the container restarts?
Seeing as this issue appears to still be present, for anyone else stumbling upon this issue it seems that the Azure load balancer resource itself may be taking the first configured static IP address.
GitHub issue response:
the first public IP address created is used for egress traffic
Microsoft Docs:
Once a Kubernetes service of type LoadBalancer is created, agent nodes are added to an Azure Load Balancer pool. For outbound flow, Azure translates it to the first public IP address configured on the load balancer.
As far as I can tell, once you provision an IP address and configure an AKS load balancer to use it, that IP gets picked up by the provisioned load balancer resource in Azure. My best guess is that when Kubernetes attempts to provision a new load balancer with the same IP address, if the previous Azure load balancer still exists the IP config will fail as it's still in use.
Workaround was to provision an extra static IP (one specifically for the Azure load balancer resource, and one for the actual AKS load balancer service) to avoid conflicts. It's obviously not ideal but it solves the issue...
I have to create a system with JBoss in cluster modality with a load balancer using Apache HTTPD with mod_cluster.
I have configured the system correctly, and the load balancer see all nodes of the system. But, I have to create the web application for the load balancer now.
It has to be a servlet or a REST service that has a reference to a remote bean and make a lookup with JNDI? Or is something different?
Can someone provide to me a reference to a documentation/tutorial that explain that?
mod_cluster is a Apache module that does the HTTP(S) load balancing.
Read more here: http://mod-cluster.jboss.org/
The whole application is installed in JBoss mod_cluster just does the load balancing.
mod_cluster is just for load balancing. Just deploy the web app against the server group created. It gets deployed on master and slaves and can access the remote bean as required.
You can dig into our mod_cluster testing servlets on clusterbench/clusterbench or vastly simplified, lobotomized version.
All new documentation effort is accumulated on: http://modcluster.io
TL;DR
create any servlet application
deploy to your workers and it's good to go
if you want web sessions replicated in the cluster, add <distributable/> to your WEB-INF/web.xml
I'm having a problem to run and exe from my browser using ActiveX.
I have Apache balancer and 4 ManagedServer on Weblogic.
The problem is:
Browser---> ServerA IT WORKS open my exe
Browser---> Apache-Balancer---> Server(A,B,C,D) random server DOESN'T WORK my exe doens,t run.
Any help?
Thanks
Carlo
Are you using proxy balancer for load balancing? There might be possibility that session stickiness is not working .Try to configure Apache and weblogic using wls web server proxy plugin for apache which is designed for weblogic load balancing and by default having session stickiness enabled.
Check below link
Http://Middlewaresnippets.blogspot.in/2015/05/working-with-apache-http-server.html
I'm totally new to clustering and load balancing.
What I'm trying to do is "Deploy Application on a Cluster which contains 2 managed servers. Now, If one of the managed server goes down, request should be redirected to another server which is Up."
For Example:
I've 2 managed servers (M1:7021 and M2:7022)
And I've a Cluster C1 having M1 and M2.
And I've an Application App1 deployed on C1 and a Data Source deployed on C1.
Application App1 is working fine.
The way through which I'm accessing application is:
http://10.184.111.11:7021/App1/
AND
http://10.184.111.11:7022/App1/
Now, Suppose if M1(7021) goes down, and request is coming like
:7021/App1/
Then, it should be redirected to :7022/App1/
Any help is highly appreciated. Thanks!
I believe you will need a load balancer (or a software equivalent) to sit above the weblogic servers and direct traffic down to those servers.
The idea being that you access your application on http://loadBalancer.com/App and then the Load Balancer forwards your request onto either one of weblogic servers. Meanwhile in the background the load balancer is continually performing health checks on the two weblogic servers to see if they are running.
In the event that one of the weblogic servers go down, the load balancer will mark it as inactive and forward all traffic to the weblogic server still running. Once the failed weblogic server has come back online the load balancer will begin routing traffic back through it.
#Garreth Well, in fact WebLogic DOES provide an internal load balancer. You are supposed to use OHS or Apache for load balancing in production environments, but for development, httpclusterservlet works great.
I am using apache load balancer 2.1 with JBOSS where I have configured 10 jboss nodes to be managed by apache load balancer. Is there any console available in apache load balancer to manage all these nodes and see how many users are handled by each of these nodes when there is some load on the environment?
There is a JKManager console. It is not something mind blowing, but is quite useful.
See:
http://tomcat.apache.org/connectors-doc/generic_howto/loadbalancers.html
http://www.gesea.de/en/techdocs/admin/tomcat/JKManager-Apache-mod_jk-loadbalancer-status-monitor.htm