Can you explain how to access the management dashboard when in cluster mode? As soon as second instance comes online, the dashboard no longer works, it just redirects back to the login screen after logging in.
If you use a load balancer and trying to access the dashboard from the load balancer, you should use a sticky session.
For HAProxy: https://www.haproxy.com/blog/load-balancing-affinity-persistence-sticky-sessions-what-you-need-to-know/
Related
I'm having a very tough time getting this to work. We are using SSRS to view reports on our internal network. However, I would like to deploy SSRS so users from home can use it since we're working from home more frequently. I will supply a screenshot of the current config with the App Proxy settings and maybe you can point something out that I am doing wrong because I'm lost at this point and google has stopped helping.
At this moment, I am trying to deploy SSRS using App Proxy from Azure, however, if you know another way, please let me know.
Again, this is a simple deployment. We simply access SSRS using a http/s address internally and it works fine. I just want users to be able to use it from Home through a website.
App Proxy Settings
App Proxy Cont.
This ended up being a bit of a journey.
Do not install your AD Connect or App Proxy connectors on a Domain Controller. Put them on the same virtual server by themselves.
Set up your SQL Server and Oracle all under a domain service account. If you haven't done this already, get ready to reinstall because it's likely that manually switching the SPN keys isn't going to work.
Leave the default App Proxy settings alone when you Configure App Proxy.
If you have a weblink like reporting.domain.com/reports in Azure you MUST make sure you have reporting.domain.com/reports/ do not forget the extra / at the end.
App Proxy with SSRS will now work.
Use this as your overall guide
https://learn.microsoft.com/en-us/power-bi/report-server/azure-application-proxy
I am trying to test a api with the help of jmeter through aws load balancer it throws 504.And the instance cpu reached 100% and it is not getting drop till restarting the server.
Same api tested with the help of postman through aws load balancer it throws the expected output.
Same api tested with the help of jmeter hitting directly to the instance(voilated load balancer) throws the expected outupt.
I am facing the issue only hitting via load balancer through JMETER.
I am not facing the issue
While hitting via load balancer through postman
Hitting without load balancer directly to the instance through JMETER.
so how to overcome the issue with jmeter and loadbalancer
Try adding a DNS Cache Manager to your Test Plan, it might be the case that JMeter hits only one node behind the load balancer and remaining nodes are not touched by the load test.
References:
Disable DNS caching
The DNS Cache Manager: The Right Way To Test Load Balanced Apps
Other causes could be connected with load balancing mechanism and/or algorithm, the load balancer can orchestrate the requests basing on cookies so you will need to play with the HTTP Cookie Manager, or source IP address or whatever.
I'm building an app that will call a web service that has 2 identical instances, each running on a different server, with its own IP.
The app can call any service instance at any time, but sometimes it may have difficulties getting a response from one of them (because of a network failure or a problem with the instance).
What is the recommended way to make the app automatically stop using the problematic instance?
How can it get back to using the instance when it's online again?
Are there standard libraries or tools to help this kind of scenario?
Use a load balancer.
You app will have to connect to the LB and not to the web servers directly. LBs maintain status of each server they are configured with ( through timeout or explicit http status calls). They automatically disable traffic from the disconnected servers and enable it once the instance is back.
Later on you can add or remove instances based upon your requirements ( manual or auto-scaling ) without requiring any changes in your app.
HAProxy and Nginx are widely used for internet scale load balancing. Cloud providers also provides this as a service, you can use them if you are on cloud ( like AWS has elastic load balancing, Google Cloud has Load Balancing ).
Noob Question:
I have a Jenkins instance setup on an internal team domain (with our own DNS/AD configured). This domain is inside the intranet.
We have security enforced on Jenkins using the Active Directory plugin. Therefore, all users login with their AD credentials for an actions like triggering a job, etc. Viewing is open to all.
We access the Jenkins instance using the DNS name (http://jenkins.team.company.com:8080). However, when accessing certain jobs, the address changes to http://10.XX.XX.XX:8080/../..). At this point, the users' logged in sessions are also terminated.
I am at a loss about what is causing the sessions to get lost.
(in the spirit of full disclosure - this Jenkins instance does not have an nginx or apache running in front of it. Until recently, this was my own local Jenkins instance but now the ask is to get everyone to start using this. I am wondering whether setting up nginx or Apache will resolve the problem. You can tell that I have none or very little background with running Web Applications)
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.